Metricbase insert

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations do declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), so the mutation aspect is partially covered by structured data. However, the description adds nothing beyond this – no mention of what data is written, auth requirements, batching behavior, or side effects for what is evidently a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but that brevity reflects under-specification rather than conciseness; it earns no informational value. There is no front-loaded purpose, scope, or routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no output schema and zero schema description coverage, the description is entirely inadequate. Nothing an agent needs to call this tool correctly – parameter formats, required combos, or side effects – is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Six parameters (sys_id, values, end_time, start_time, table_name, metric_name) are documented at 0% coverage in the schema, and the description supplies no meaning whatsoever for any of them. The agent has no way to know what 'values' should contain or how metric_name/table_name relate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Invoke the metricbase_insert operation' is a tautological restatement of the tool name and title; it names no verb-resource pair an agent could reason about. It gives no indication of what is being inserted, into what system (metricbase), or how it differs from siblings like servicenow_ingest_cmdb_data or servicenow_add_table_record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to, or which sibling to prefer. The description contains no context, prerequisites, or alternatives, leaving the agent to infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.