get_procedure_source

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

Describes return type (raw PSQL body text) and error behavior. No annotations provided, so description carries full burden; it adds useful behavioral context like automatic uppercasing.

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?

Two sentences with no extraneous information. Front-loaded with purpose, efficiently structured.

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?

Fully describes inputs, constraints, and output for a simple two-parameter tool. No output schema needed; description covers return type adequately.

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?

With 0% schema description coverage, the description explains both parameters: database as key from list_databases, procedure as name from list_procedures with uppercasing. Adds meaning beyond type-only 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?

Explicitly states 'Return the full PSQL source body of a stored procedure', clearly identifying verb and resource. Distinguishes from sibling tools like get_trigger_source and get_view_source.

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?

Explains how to obtain parameter values from list_databases and list_procedures, including automatic uppercasing. Lacks explicit when-not-to-use or alternatives, but context is sufficient for a simple retrieval tool.

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