query_analytics

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

No annotations provided, so the description must fully disclose behavior. It describes what the tool does but does not state it is read-only, whether it modifies data, requires authentication, or has rate limits. The agent lacks insight into side effects or safety.

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 structured as a docstring with a clean arg list. It is relatively concise and front-loaded with the main purpose. Minor redundancy could be trimmed (e.g., repeating 'YYYY-MM-DD format' is fine).

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?

The tool has 5 parameters and an output schema (unknown content). The description covers input behavior well, but omits behavioral details (read-only, pagination, error handling) and does not mention what the output schema provides. It is adequate but not fully complete.

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?

With 0% schema description coverage, the description adds substantial meaning to all 5 parameters: view's options and descriptions, date format, month format, source examples, and limit default. This fully compensates for the bare 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?

The description clearly states the tool queries analytics across specific views (timeline, stacks, problems, spend, summary), with a specific verb 'query' and resource 'analytics'. It distinguishes itself from sibling tools that focus on conversations, searches, and other areas.

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 provides explicit use cases for each view (e.g., 'What happened on a specific date' for timeline), but does not explain when to use this tool over siblings or when not to use it. No alternatives or exclusions are mentioned.

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