get_task

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

With no annotations provided, the description carries the disclosure burden. It lists the exact fields returned (description, file extensions, extra materials, deadline, submitted reports), giving transparency into the tool's behavior. It does not mention read-only nature or auth, but for a simple get, this is adequate.

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 that front-loads the purpose and immediately lists the included details. It is concise, with no filler or redundant information.

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?

The description lists the key return fields, which is helpful given no output schema. It does not cover error scenarios or how to obtain the task_id, but for a simple get tool with one parameter, it is fairly complete. A slightly richer description of the report statuses or potential errors would earn a 5.

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 schema only has 'task_id' as a string, but the description adds that it is a 'numeric ID', providing extra semantic detail. This is meaningful given the 0% schema coverage, though it could clarify the format (string of digits) to avoid confusion.

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 full details) and the specific resource (a task) with a scope limitation (by numeric ID). It distinguishes itself from list_tasks, which likely lists all tasks, making it clear this tool targets a single 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?

The description implies usage when needing details for a specific task, contrasted with list_tasks for listing. However, it does not explicitly mention alternatives or when not to use the tool, so it lacks an explicit 'use this instead of...' guidance.

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