Compare collections

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context beyond annotations: auto-detected key matching, composite keys, per-list paging, unknown-item handling, and the strict=false relocation behavior.

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 front-loaded with the core purpose and uses compact clauses without filler. Every sentence contributes to purpose, behavior, or usage context, and the information is organized logically.

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 9-parameter comparison tool with no output schema, the description explains the two operating modes, matching semantics, paging, and result categories. It could say more about the exact response shape, but it is complete enough for an agent to invoke 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 coverage is high at 89%, giving a baseline of 3, but the description adds value by clarifying key auto-detection and composite syntax, the list/offset paging model, and the optional collection mode. It still leaves some parameters such as ignore and limit mostly to the schema.

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: 'Diff one collection between two targets,' and enumerates the result categories and key-matching behavior. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as hexvero_collection or hexvero_list.

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?

It gives useful usage context by explaining the no-collection mode: 'Without collection: counts per shared collection, to pick one,' which implies a discovery-then-compare workflow. It does not name alternatives or exclusions, so it falls short of a full when-to-use/when-not-to-use guide.

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