get_analytics

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

No annotations are present, so the description carries the full burden. It does not disclose whether the tool is read-only, if there are any side effects, rate limits, or authorization requirements. The description only mentions retrieval, which implies non-destructive, but this is not explicit.

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 concise and front-loaded, presenting the tool's purpose in the first sentence. It uses a simple structure, though the arguments section is redundant with the schema. Still, it avoids unnecessary verbosity.

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 presence of an output schema (not shown but indicated), the description does not need to explain return values. However, it lacks usage guidelines and behavioral transparency, which are important for a tool that only has one parameter. It is minimally adequate.

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 includes an arguments section repeating the parameter name and type, but with 0% schema description coverage, it adds no meaningful context beyond what is already in the input schema. No additional constraints, examples, or formatting details are provided.

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 retrieves performance analytics for a workflow, listing specific metrics (success rates, latency, cost, model usage). It uses a specific verb ('Get') and resource ('analytics'), and the provided metrics distinguish it from other tools like get_runs or get_workflow.

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 guidance is provided on when to use this tool versus alternatives like get_runs or get_run_summary. The description lacks any contextual hints about prerequisites or when it is appropriate to call this tool.

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