create-spans-metric

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

Annotations provide basic safety profile (non-read-only, open world). The description adds no further behavioral details such as side effects, permissions, or whether the metric persists. With openWorldHint=true, more context would be helpful.

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 description is a single 12-word sentence that front-loads the key purpose. Every word earns its place; no wasted content.

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?

Given the tool's complexity (6 parameters, nested groupBy) and absence of output schema, the description covers the core function. It could mention persistence or querying, but it is adequate for a creation tool with a clear schema.

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?

Schema coverage is 100%, so the description does not need to add much. It restates the aggregation types but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool creates a metric from APM span data, specifying aggregation types (count/distribution) and mentioning filters and group-by. It effectively distinguishes from sibling tools like create-logs-metric and create-rum-metric.

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?

The description implies usage for APM span data, which is sufficient context. However, it does not explicitly state when not to use it or list alternatives, but the domain is clear.

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