show_create_procedure

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

With no annotations, the description alone must disclose behavioral traits such as read-only nature or permission requirements. It only states the action (return DDL) without any safety or side-effect information, leaving the agent unaware of potential risks.

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 extremely concise at one sentence, front-loading the core purpose. However, it could include a bit more context without significant bloat, such as a brief note on output format.

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 lack of output schema and the tool's purpose (returning DDL), the description should at least hint at the response structure (e.g., 'Returns the SQL text as a string'). It also omits error conditions or permission notes, making it incomplete.

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?

Despite 67% schema coverage, the description adds no additional meaning to the parameters. For example, it does not explain the format expected for the 'procedure' parameter (e.g., fully qualified name versus simple name) or any constraints beyond the schema.

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 'Return CREATE PROCEDURE DDL' uses a specific verb and resource, clearly indicating it retrieves the DDL for a stored procedure. This distinguishes it from siblings like show_create_function and show_create_table, which target different object types.

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. The description does not mention cases where show_create_function or other tools would be more appropriate, nor does it state any prerequisites or exclusions.

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