payload_index_create

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

The annotations already communicate non-read-only and non-destructive behavior. The description additionally clarifies that creating an index enables fast filtering, but it does not disclose what happens if the index already exists or whether this affects existing data. This is adequate but not rich.

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 two sentences, front-loads the core action, includes examples, and adds a practical usage condition. There is no fluff or repetition of schema details.

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?

The tool is a moderately simple three-parameter mutation and the description conveys its purpose and why to use it. However, because schema description coverage is 0%, the description should have provided more direct guidance on the value domains and how to populate the parameters correctly.

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 0%, so the description carries the burden of explaining the parameters. It broadly refers to a field such as date, author, or type, but it does not explain the exact meaning of collection, how field_type should be chosen, or how the parameter values relate to each other.

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 a specific verb and resource: 'Creates a payload index on a collection field' and gives the intended purpose ('fast search filter'). It does not just restate the tool name and it is clearly distinguished from collection creation and search tools.

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 gives an explicit trigger: use this when the wizard's filter question or a user request names a field that needs to be filterable. It provides clear context, though it does not explicitly say when not to use it or name an alternative tool.

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