get_task

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

The description labels the tool as 'FREE' and 'Undocumented endpoint', hinting at cost and reliability characteristics. However, it lacks details on read-only behavior, error responses, or required permissions, leaving significant behavioral gaps.

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 description is a single sentence with no fluff. It directly states the purpose and adds two metadata tags ('FREE', 'Undocumented endpoint') without sacrificing clarity.

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 get-by-ID tool, the description is minimally adequate but lacks details on return value, error handling, and prerequisites. The 'undocumented endpoint' note introduces uncertainty about stability.

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% for the single parameter ('Apollo task ID'). The description adds no further meaning beyond the schema, so baseline score applies.

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 clearly states the action ('Get a single task by ID') and identifies the resource (task). It specifies the identifier method, but does not differentiate from sibling tools like 'search_tasks' or 'update_task'.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that this tool retrieves a single task by ID while 'search_tasks' may be used for filtering or listing tasks.

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