create-spans-metric

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

No annotations are provided, so description must carry full behavioral burden. It indicates creation of a metric but does not disclose side effects, permission requirements, or whether the operation is idempotent. Minimal transparency beyond the action.

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?

Single sentence effectively communicates the tool's purpose and key capabilities. It is concise without unnecessary details, though could benefit from a brief example or structure hint.

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?

No output schema or annotations, so description must provide sufficient context. It covers the metric source and types but lacks details on return values, error states, or the relationship between the created metric and the 'id' parameter. Adequate but not fully complete for an agent to use autonomously.

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?

All 6 parameters have schema descriptions covering 100%. The description adds high-level categories (count/distribution, filters, group-by) but these concepts are already captured in the schema. The description does not significantly enhance parameter meaning beyond the schema.

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?

Description clearly states creation of a metric from APM span data, specifying the two aggregation types and the ability to add filters and group-by. Distinguishes from sibling tools like 'create-logs-metric' and 'create-rum-metric' by specifying 'APM span data'.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for span-based metrics, but does not compare with logs or RUM metric creation. Sibling tool names provide some context, but description alone lacks directive.

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