collection_info

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no contradiction exists and the read-only nature is known. The description adds detail about the returned fields, which is helpful, but does not disclose additional behavioral traits such as error behavior, required permissions, or rate considerations.

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 compact: two sentences with no filler. The first sentence states what the tool returns, and the second gives a concrete use-case. Information is front-loaded and every clause earns its place.

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?

For a simple read-only tool with one parameter, an output schema, and clear annotations, the description provides enough for an agent to select and call it correctly. It could mention what happens when the collection does not exist, but this is a minor gap given the output schema exists.

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?

There is only one required parameter, 'name', and the schema description coverage is 0%. The description clarifies that the name refers to one collection, but does not explain naming constraints, formats, or how the value is used beyond the title already indicating it is a name.

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 uses a specific verb and resource: 'Returns full detail on one collection,' and enumerates what is included: vector schema, payload indexes, size, and optimization status. This clearly distinguishes it from sibling tools like collection_list or collection_create.

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 explicitly states when to use the tool: to inspect a specific collection's configuration, with a concrete example — deciding whether hybrid search or a given filter is available. It does not explicitly describe when not to use it or name alternatives, but the usage context is clear.

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