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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact: results are scoped to data visible to the linked Market Brew account. It omits any error behavior for an unknown taskId or what the returned record contains.

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, no filler, with the purpose front-loaded before the scoping note. Efficient, though the first sentence is partly redundant with the tool name and 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 simple single-parameter read tool with no output schema, the description is minimally adequate: safety is covered by annotations and account scoping is stated. The gaps are the undocumented taskId and the absence of any statement about what the tool returns or how it fails.

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 0% and the single required parameter (taskId) is never mentioned in the description. The schema shows taskId accepts a string or number but gives no format hints; the description does nothing to compensate or explain where a valid task ID comes from.

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?

States a specific verb ('get') and resource ('a Ranking Sensor task'), which distinguishes it from sibling metric/history tools like get_task_metrics and get_task_history. It does not, however, clarify how it differs from list_tasks or list_task_children, so sibling differentiation is only partial.

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 only guidance is 'Use this when the user asks to get a Ranking Sensor task,' which simply restates the tool's purpose as a trigger phrase. There is no mention of when to prefer it over list_tasks/get_task_history, nor any prerequisite (e.g., needing a taskId obtained elsewhere).

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