ag_data_dedupe

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

With no annotations provided, the description fully carries the transparency burden. It discloses determinism, fixture verification, guest availability, rate limiting, the api_key role, output format, and that it returns a Guild-signed provenance envelope. This gives a clear picture of behavior and side effects.

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 generally well-structured and informative, but there is minor redundancy between 'Deduplicate JSON records' and 'Removes duplicate records.' It remains compact enough while conveying all necessary behavior and 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 description includes the output schema and explains the returned result plus provenance envelope. It covers input requirements, optional parameters, and semantics such as JCS-canonical equality and case-insensitivity, making the tool fully understandable without additional documentation.

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?

Although the input schema has no per-property descriptions, the description explicitly explains the payload schema: records, optional keys, and optional case_insensitive. It also explains the api_key parameter in the context of rate limits and member budgets, fully compensating for the schema's lack of descriptions.

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 identifies the tool's action: deduplicate JSON records exactly, with optional key-subset and case-insensitive behavior. It also provides specific ordering semantics (first occurrence kept, order preserved), making the purpose unambiguous.

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 clearly indicates when to use the tool: whenever exact deduplication of JSON records is needed, including by a chosen key subset. It does not explicitly contrast alternatives like ag_data_record_link, but the exact-vs-fuzzy distinction is implied by the word 'exactly' and the detailed behavioral description.

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