list_procedures

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

No annotations provided, but description states it lists procedures and returns names, implying read-only. Does not detail permission needs or performance, but the behavior is clear enough for a listing tool.

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 front-load the purpose and then explain parameters with sibling reference. Zero wasted words; very 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?

Given no output schema, description mentions return value (procedure names) and links to sibling for body. Parameters are explained. Could mention error handling or limits, but core information is present.

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?

No schema descriptions, but description compensates by explaining database is a key from list_databases and filter is an optional regex. This adds meaningful context beyond the schema's type and requirement.

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 'list all user-defined stored procedures', specifying verb and resource. Distinguishes from siblings by mentioning get_procedure_source for reading body, and implies scope (user-defined).

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?

Tells database should be key from list_databases (sibling), explains filter is optional case-insensitive regex, and directs to use get_procedure_source for full body, effectively guiding when to use this vs alternative.

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