collection_stats

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

No annotations provided, so the description must stand alone. It only states the basic operation without disclosing behavior like side effects, permissions, or error states. The deprecation warning adds some behavioral context, but overall disclosure is minimal.

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?

Extremely concise: one short sentence with a deprecation warning. No unnecessary words, and the key information is front-loaded.

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 deprecated, parameterless tool with an output schema, the description is sufficient but lacks explanation of what 'index statistics' entails. The agent might need to rely on the output schema for full understanding.

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 are no parameters, and schema coverage is trivially 100%. The description adds no additional semantics, but none are needed. Baseline score of 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 states 'Get index statistics' and deprecates itself in favor of 'stats'. It clearly communicates the resource and action, and distinguishes from the sibling tool 'stats'.

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?

Explicitly recommends using 'stats' instead, providing clear guidance on when to avoid this tool. However, it lacks details on any specific contexts where using this deprecated tool might still be necessary.

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