call_procedure

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

Without annotations, description fails to disclose side effects, permissions, error handling, or mutability. Only mentions result and OUT parameter capture, insufficient for a DB procedure invocation.

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, no filler, front-loaded. Could include more detail without losing conciseness, but current structure is efficient.

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?

Lacks info on permissions, error handling, return volume, or how to use OUT parameters. No output schema; description does not compensate for complexity of stored procedure calls.

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?

Adds context for 'params' as JSON; but 'procedure' parameter remains undocumented. Schema coverage is 50%, so description partially compensates but not fully.

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?

Clearly states verb 'Call', resource 'stored procedure', and mechanism 'with JSON params; captures result sets and OUT parameters'. Distinguishes from siblings like 'call_function' and 'execute'.

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?

Implies use for stored procedures with JSON params, but no explicit when-to-use or when-not-to-use compared to other tools like 'call_function' or 'execute'. No alternatives mentioned.

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