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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add two useful behaviors: participant details (my_application, assignment, next_step) appear only under some condition described as "with a key," and confirm_url appears when owner action is required. Those are real disclosures, but the conditional phrasing is ambiguous enough that the agent cannot confidently predict the response 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?

It is short, but the semicolon-and-parenthetical fragment structure is hard to parse and the words saved come at the cost of clarity. Brevity here is under-specification rather than economy.

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 one-parameter read tool with no output schema, the description should at least describe the returned task shape or when confirm_url/participant fields appear. Instead it gestures at these conditionally and never explains the identifier, leaving notable gaps for an agent deciding whether to call it.

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%, so the description carries the burden for the single parameter. It never explains task_id or that it is a UUID, and "a key" reads as an auth/API key rather than a parameter, which adds confusion instead of meaning.

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?

"One task" signals single-resource retrieval, and the mention of participant data and confirm_url hints at what comes back, so the resource is identifiable. But the verb is only implied by the tool name and the phrasing is telegraphic, leaving the agent to guess that this is a fetch-by-id operation rather than something else.

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?

There is no statement of when to use this versus search_tasks or get_rules; the only routing clue is the implicit contrast between "One task" and a search. "With a key also participant" is too cryptic to count as usage guidance.

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