list

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

No annotations are provided, so the description carries the full burden. It discloses that 'collection' only applies to 'documents,' which is useful conditional behavior. However, it does not mention other behavioral traits such as read-only nature, pagination, ordering, or potential side effects. For a listing tool, this is adequate but not comprehensive.

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?

The description is concise and front-loaded with the main action, followed by a neatly structured Args section. Every sentence provides necessary information, with no filler or redundant content.

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 presence of an output schema, the description need not explain return formats. It adequately covers the tool's flexibility (various kinds and optional filter) and is sufficiently complete for a listing operation. It lacks details on pagination or ordering, but these are not always required and are likely captured by the output schema.

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?

The schema has 0% description coverage, but the description compensates fully by defining allowed values for 'kind' ('documents', 'collections', 'databases', 'registrations') and explaining the conditional behavior of 'collection' (only for kind='documents'). This adds significant meaning beyond the bare schema properties.

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 begins with 'List documents, collections, databases, or registrations,' clearly stating the tool's function with a specific verb and resource types. This distinguishes it from sibling tools like 'find' and 'show' by focusing on enumeration rather than search or detail retrieval.

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?

The description provides a clear context for when to use the tool: whenever you need to list any of the four resource types. It does not explicitly exclude alternatives or mention when not to use it, but the purpose is sufficiently clear to guide basic usage. The condition on the 'collection' parameter adds some contextual guidance.

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