itglue_scan_duplicates

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

Reveals capping at 5000 records, default threshold of 0.85, and return structure (groups of 2+). No annotations exist, so description carries full burden. Lacks error behavior but sufficient for core 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?

Three sentences, front-loaded with main purpose, followed by constraints and returns. No unnecessary words; every sentence adds value.

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, description mentions return type (groups 2+ records). Covers constraints and recommendations. Minor missing details on failure cases but adequate for a scan tool.

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%, baseline 3. Description adds context beyond schema: explains organizationId for narrowing, threshold default, and pageSize/maxPages bounding. Adds meaning to parameters.

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?

Clearly states verb 'scan' and resource 'IT Glue resource type' with specific purpose 'find likely duplicate records by pairwise name similarity'. Distinguishes from siblings like search/find 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?

Description provides some guidance: 'Useful for cleanup audits', capping suggestion, and narrowing by organizationId. But no explicit when-not-to-use or comparisons to alternative matching tools (e.g., itglue_find_contact_match).

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