get_tag_statistics

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It discloses the return type (tag statistics including task counts per tag), which implies a read-only aggregate operation, but it does not explicitly confirm lack of side effects, permissions, or rate limits. This is a minimum viable disclosure for a simple getter.

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 concise sentences, each earning its place. It front-loads the primary purpose and then provides a helpful return-value summary. 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?

Given the simplicity (no params) and the existence of an output schema, the description is mostly complete. It mentions the key outcome (task counts per tag) and the 'all tags' scope. The only gap is lack of differentiation from get_statistics, but this doesn't significantly undermine completeness.

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?

There are zero parameters, and schema coverage is 100% (empty schema). The description adds semantic meaning by clarifying the scope is 'all tags', which is useful context beyond the empty schema. Baseline for 0 params is 4, and this is appropriately scored.

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 gets statistics for all tags, with a specific scope ('all tags') and a detail on the return value ('task counts per tag'). This distinguishes it from sibling tools like list_tasks and get_statistics by focusing on tag-specific aggregation.

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 no guidance on when to use this tool versus alternatives. It does not mention that get_statistics might be a broader alternative or when a tag-specific stat is preferred. No exclusions or prerequisites are stated.

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