List Stored Procedures

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

With no annotations, the description must disclose behavioral traits. It only states the tool lists basic information but does not mention default behavior for parameters (e.g., whether system objects are included by default) or performance implications. The tool is read-only, but this is not stated.

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, front-loaded with action and resource, no redundant words. Efficient and to the point.

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, the description could elaborate on what 'basic information' includes (e.g., name, schema, type, creation date). It also does not mention whether the results are paginated or limited. However, it is adequate for a simple listing tool.

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 description coverage is 100% (all 3 parameters have descriptions). The tool description does not add additional meaning beyond the schema; it only summarizes the overall function. 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 'List all stored procedures, functions, and their basic information' clearly states the tool's action (List), resource (stored procedures and functions), and scope (basic info). It distinguishes from siblings like 'describe_stored_procedure' which gives detailed metadata, and 'get_all_stored_procedure_definitions' which returns full definitions.

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 explicit guidance on when to use this tool vs alternatives like 'describe_stored_procedure' or 'get_multiple_stored_procedure_definitions'. The description does not mention when to choose this tool over similar list tools such as 'list_functions' or 'list_triggers'.

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