get_task

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

With no annotations, the description must convey safety and behavior. It merely says 'Get detailed information' without indicating read-only nature, authentication needs, or potential effects. The agent is left guessing whether this modifies data.

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?

While short, the description is not optimally concise: it repeats schema info in an 'Args' section without adding insights. A single sentence stating purpose and implying a required ID would be more efficient.

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 a single parameter and the presence of an output schema, the description still lacks completeness by omitting usage context, behavioral guarantees, and parameter details. It is minimal but insufficient for confident use.

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 description adds no value to the schema: it simply restates 'ID of the task', which is already clear from the parameter name and type. Since schema coverage is 0%, the description fails to provide examples or valid formats.

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 explicitly states the action ('Get detailed information') and resource ('a single task'), clearly distinguishing it from sibling tools like create_task or get_tasks which serve different purposes.

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 is provided on when to use this tool versus alternatives such as get_tasks or search_task_by_name. The description does not clarify that it retrieves only one task by ID, assuming the agent knows the difference.

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