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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds that completed results are included and gives the REST key-lookup route, but does not discuss pagination, auth, or rate limits; with annotations in place this is modest added context.

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 definition is front-loaded and compact, moving from the core retrieval action to lookup modes and then to the REST endpoint detail. Every sentence contributes without repetition.

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?

With a rich annotation set and an output schema, the description does not need to cover return values. It is complete enough for a read-only retrieval tool with three optional parameters, though it could clarify tool-selection boundaries versus mutating siblings.

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 coverage is 100%, so baseline is 3, but the description adds meaningful lookup semantics: id works in both REST and MCP, while namespace+task_key is described as an MCP path, with a REST query example. This goes beyond the generic schema descriptions, though the parenthetical '(MCP)' next to namespace/task_key while also describing a REST key lookup is slightly confusing.

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 ('Retrieve') and resource ('a task'), and enumerates the two supported lookup modes. The retrieval framing distinguishes it from action siblings like claim_task and complete_task, though it does not name them.

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?

Explains which parameter combinations are valid (id via REST or MCP; namespace/task_key via MCP) and gives the REST endpoint for key lookup. However, it offers no explicit guidance on when to choose this tool over alternatives such as claim_task or complete_task.

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