Tool Analytics Dashboard (Legacy)

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds context about the summary_only parameter returning sample point IDs for fetching specific results, which clarifies the tool's return behavior beyond the annotations.

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 two sentences: the first clearly states the purpose, and the second explains the default behavior and how to adjust it. It is front-loaded and concise with no wasted words.

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 an output schema (unseen) and a boolean toggle. The description mentions sample point IDs for fetching specific results, which is a key behavioral detail. It covers the main functionality sufficiently, though it could explicitly mention the output schema's role.

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 description coverage is 80% (4 of 5 parameters have descriptions). The description adds value by explaining the effect of summary_only (default summary, set false for detailed data) but does not provide additional meaning for other parameters beyond what the schema already offers.

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 explicitly states it gets comprehensive analytics on tool usage, performance metrics, and patterns. It distinguishes between summary and detailed data. However, it does not differentiate from sibling tools, which is acceptable given its unique purpose.

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 analytics queries, mentioning default summary behavior and how to get detailed data. It does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives.

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