Get All Stored Procedure Definitions

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

No annotations are provided, so the description must disclose behavioral traits. It only states it retrieves definitions, but fails to mention whether it requires permissions, is read-only, or has any side effects. The agent lacks awareness of the tool's safety profile.

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 of 10 words, front-loading the key action and resource. Every word is necessary, and there is no redundancy or wasted 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?

Given the absence of annotations and output schema, the description is minimal. It does not explain return format, pagination, or parameter behavior (e.g., default schema, maxResults). Adequate but leaves gaps for a tool with 4 parameters.

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 coverage is 100%, so all parameters are documented. The description adds no additional meaning beyond what the schema provides. It mentions 'in a schema' but the schema parameter already covers that. Baseline 3 is appropriate.

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 verb 'Get', the resource 'complete SQL definitions for all stored procedures', and the scope 'in a schema'. It effectively distinguishes from sibling tools like 'get_stored_procedure_definition' (single) and 'get_multiple_stored_procedure_definitions' (multiple, but not all).

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 for retrieving all procedure definitions, but it does not provide explicit guidance on when to use this tool over alternatives like 'get_multiple_stored_procedure_definitions' or 'get_stored_procedure_definition'. No when-not-to-use or exclusion criteria are mentioned.

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