get-stored-procedure

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

No annotations exist. Description lacks behavioral details such as behavior when UUID is not found, authorization requirements, or whether it returns full details or only metadata. For a read operation, basic transparency is still missing.

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?

Single sentence is concise and front-loaded. No unnecessary words, but could be slightly more informative without adding length.

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?

No output schema provided, yet description does not mention return value or structure. For a retrieval tool with 3 parameters and no annotations, it lacks completeness.

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?

Schema description coverage is 67% (id and fields have descriptions; include has enum but no description). The description adds no meaning beyond the schema; it only restates the required id parameter. Baseline 3 given high 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?

Description clearly states verb (get), resource (stored procedure details), and method (by UUID). However, it does not differentiate from sibling get-stored-procedure-by-name, which retrieves by name instead of UUID.

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 provided on when to use this tool versus alternatives like get-stored-procedure-by-name or list-stored-procedures. No exclusions or context given.

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