cmdb_find_duplicates

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

Annotations already declare readOnlyHint and openWorldHint. The description adds 'in-memory grouping', clarifying the operation does not modify the database. This provides extra context beyond annotations.

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?

Single sentence with no filler. Concise yet packs the core purpose and key behavioral trait (in-memory grouping).

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 no output schema and 3 well-documented parameters, the description covers the essential purpose and context. Minor omission: not specifying return format or duplicate criteria, but annotations compensate.

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 100%, so parameters are well-documented. The description mentions 'specified fields' which relates to match_fields, but adds 'in-memory grouping' as behavioral context. Meets baseline for high coverage.

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 clearly states 'Find duplicate CIs by matching on specified fields', specifying the verb (Find), resource (CIs), and action (grouping duplicates). It differentiates from sibling tools like cmdb_find_orphans by focusing on duplicates.

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 implies usage for duplicate detection but lacks explicit guidance on when to use this tool versus alternatives (e.g., cmdb_find_orphans). No when-not or context about prerequisites.

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