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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds one useful piece of context beyond that - that results are scoped to the linked Market Brew account - but does not address pagination, ordering, or the return shape.

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 with no filler; the trigger condition is front-loaded and the access-scope caveat follows. Well-sized, though the first sentence is somewhat redundant with the title.

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 read-only list tool with no output schema and full schema coverage, the description covers the essential trigger and access scoping. It lacks pagination/ordering guidance, but nothing critical to calling it correctly is missing.

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%: the single 'query' param is documented with a full list of filters. The description adds no additional parameter meaning, so the baseline 3 is appropriate for schema-led parameters.

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 states a clear verb (list) and resource (historical Ranking Sensor tasks), which partially distinguishes it from siblings like list_tasks, list_task_children, and get_task_history. However, the phrasing closely mirrors the title ('List historical Ranking Sensor tasks'), so it does little beyond restating it rather than sharpening the distinction from adjacent history/task tools.

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?

It provides a trigger condition ('when the user asks to list historical Ranking Sensor tasks'), which gives implied usage. But it names no alternatives (e.g., get_task_history, list_tasks) and states no exclusions, so the agent must infer when this tool beats its siblings.

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