List functions

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

Annotations already declare readOnlyHint=true, so the description does not need to repeat safety. The description adds context about the return structure but no additional behavioral traits (e.g., no mention of ordering, limits, or side effects). With annotations, the bar is lower, so a score of 3 is appropriate.

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-loaded with purpose, no wasted 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?

Description explicitly states what is returned (list of objects with name, kind, arguments, returns, language). Since output schema exists, the description could rely on it, but it adds clarity directly. Combined with annotations and schema, the tool is fully documented.

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 50% (only the database parameter has a description in schema). The description does not elaborate on the required 'schema' parameter or provide any additional meaning beyond what the schema already states. It does not compensate for the missing parameter documentation.

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?

Description uses specific verb 'list' and resource 'functions and procedures in a schema', and details the returned fields (name, kind, arguments, returns, language). This clearly distinguishes it from sibling list tools like list_tables, list_indexes, etc.

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?

Description clearly states it lists functions and procedures in a schema, but does not provide explicit guidance on when to use this tool versus alternatives like list_tables or list_indexes. No exclusions or prerequisites are mentioned.

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