get_task

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

Annotations are absent, so the description alone must convey behavior. 'Fetch' indicates a read-only operation, which is accurately reflected in the description. However, it does not disclose behavior for missing tasks, whether it blocks until completion, or any authentication/rate-limit requirements.

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, front-loaded sentence that states the action and resource without extra verbiage. Every word contributes to the meaning.

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?

Given the tool's simplicity (2 parameters, no output schema) and the clear schema, the description provides adequate context for a getter. It lacks explicit usage guidelines or notes about polling, but the minimal scope is acceptable; a small enhancement would be to mention it is for async task retrieval.

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?

Both parameters (action and task_id) are fully described in the JSON schema with 100% coverage. The description adds no additional semantic detail beyond the schema, so the baseline score of 3 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 uses the specific verb 'Fetch' and identifies the resource as 'the current status and latest result payload for a gemini-tts task.' This clearly differentiates it from siblings like text_to_speech (task creation) and login/check_pricing.

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 description provides no explicit guidance on when to use this tool versus siblings, such as 'use after starting an asynchronous text_to_speech task' or 'poll this endpoint for completion.' The context implies it is the retrieval counterpart to text_to_speech, but nothing in the description states this.

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