summarize_metrics

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

No annotations are provided, and the description lacks detail on behavioral traits such as read-only nature, authentication needs, error handling, or cost implications. It only hints at computation with 'summarize'.

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 very concise with three sentences, front-loading the purpose and following with syntax details. No superfluous content, but could be slightly more structured.

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 has 5 required parameters, no output schema, and no annotations, the description is insufficient. It does not explain what the output contains, error scenarios, or how this relates to other metrics tools like list_metrics.

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?

The description adds meaning for query (example syntax) and time (ISO8601 format) parameters beyond the schema's titles, but does not explain compartment_id, namespace, or exact start/end_time formats, partially compensating for zero schema coverage.

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 'Run a MQL summary' with a verb and resource, and the example query distinguishes it from sibling list_metrics by indicating it performs a summarization rather than a listing.

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 by showing query syntax and time format, but does not explicitly state when to use this tool versus alternatives like list_metrics.

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