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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact — results are scoped to the linked Market Brew account — but says nothing about aggregation, sort defaults, or pagination behavior of the metrics.

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?

Two short sentences, front-loaded with the usage trigger, with no filler. The brevity is appropriate, though the first sentence is wasted on restating the name.

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?

For a metrics tool sitting among close siblings (get_task_metrics, get_search_metrics, list_top_tasks) with no output schema, the description should distinguish scope and return shape. It leaves an agent unable to choose confidently between this and adjacent metrics tools.

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 100% and the single nested 'query' object already enumerates the filter fields (websiteId, serverHost, taskTitle, sortBy, offset, pageSize). The description contributes nothing beyond that, so the baseline 3 applies.

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?

"Use this when the user asks to get top-task metrics" essentially restates the tool name and title without adding a distinct verb+resource characterization. It never explains what a 'top task' is or how the metrics differ from get_task_metrics or list_top_tasks.

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 'when to use' clause is circular — the user asking for the thing the tool is named after is not guidance. No alternatives (get_task_metrics, list_top_tasks) or conditions are named.

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