get_procedure

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

No annotations are provided, and the description only states the lookup operation. It does not disclose whether the return includes full procedure details, error behavior, or any read-only safety guarantees. Beyond the implied read-only nature of 'Get', there is no behavioral context.

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?

A single, front-loaded sentence with no unnecessary words. It is efficiently communicated.

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 read tool, the description is minimal but omits information an AI agent would need without annotations or an output schema, such as the structure of the returned Procedure and any prerequisites or error cases. The existence of sibling tools like get_procedure_task suggests a richer context is needed.

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 'by ID' clarifies that the single 'id' parameter is the Procedure's identifier, compensating for the 0% schema description coverage. However, it provides no additional details about the ID format or constraints beyond the schema's integer type.

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 a specific verb 'Get' with resource 'Procedure' and scope 'by ID', clearly distinguishing it from list_procedures and other procedure-related tools.

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 vs alternatives like list_procedures or get_procedure_task. The description only states the operation, leaving the AI to infer usage context.

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