get_task

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to indicate whether the operation is read-only, what happens if the ID doesn't exist (404 vs null), or what fields are returned in the response.

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?

Extremely concise at 7 words with zero redundancy. The critical information (single resource, lookup key) is front-loaded and immediately scannable.

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 CRUD retrieval with one well-documented parameter and no output schema, the description is minimally adequate. However, given the lack of annotations and output schema, it should ideally mention error handling behavior or the nature of the returned data to be fully complete.

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?

The input schema has 100% description coverage ('Task ID or UUID'), and the description mirrors this exactly without adding additional semantic context (e.g., format requirements, examples, or whether UUID and ID are interchangeable). Baseline 3 is appropriate when the schema is self-documenting.

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 the specific action (Get), resource (task), and lookup method (by ID or UUID). The term 'single' effectively distinguishes it from the sibling 'list_tasks'. However, it doesn't explicitly reference sibling tools to clarify the selection boundary.

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?

Provides no explicit guidance on when to use this tool versus alternatives like 'list_tasks' (for searching without an ID) or 'create_task' (when the task doesn't exist). No prerequisites or error conditions are mentioned.

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