get_procedure_task

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

No annotations are provided, so the description alone must convey behavioral traits. 'Get' implies a read-only operation with no side effects, but the description adds no further detail such as error handling, required permissions, or what happens if the ID does not exist. It is minimally transparent but not misleading.

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 concise sentence of seven words, front-loaded with the key information: 'Get a Procedure Task by ID.' There is no wasted wording, and it is immediately scannable and understandable.

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 tool is simple with one parameter and no output schema, but the description does not state what the return value looks like or whether an error is raised on a missing record. Without annotations or an output schema, this leaves some ambiguity for an agent, but the minimal purpose is still clear. It is adequate but has clear gaps.

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 has one parameter, id, with no description. The tool description reinforces by saying 'by ID' but does not explain the nature of the ID beyond that. Since the parameter is self-explanatory and the description links it to the retrieval action, it is adequate but does not compensate significantly for the 0% schema coverage.

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 'Get a Procedure Task by ID' clearly identifies the action (get), the resource (Procedure Task), and the method (by ID). It distinguishes this from sibling tools like get_procedure (which calls on a procedure, not a task) and list_procedure_tasks (which lists, not fetches a single task by ID).

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 gives no guidance on when to use this tool versus alternatives. It does not mention that this tool is for fetching a single task by ID while list_procedure_tasks is for listing all tasks, nor does it provide any context or exclusions. The agent must infer usage from the tool name and context.

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