dedup_get

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

With no annotations, the description carries full burden. It clearly states that by default it returns metadata plus truncated previews, and setting full=True gives complete raw data. This provides a solid behavioral contract, though it avoids discussing error behavior or index bounds.

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?

Two-sentence description: first sentence states purpose, second explains default behavior and option. No extraneous text, efficient and front-loaded.

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?

Has output schema, so return values do not need detailed explanation. Description covers default vs full modes adequately. Could mention that entries are from a dedup store or index validity, but overall complete for its complexity.

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%. Description clarifies that index is 1-based and full is a boolean for full vs truncated output. However, the 'name' parameter is not explained, leaving its purpose ambiguous. The description adds value but not complete 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?

Description clearly states 'Fetch a dedup entry by its 1-based index', identifying the action and resource. It distinguishes from siblings like dedup_list (lists all) and dedup_search (searches) by specifying indexed retrieval.

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?

No explicit guidance on when to use this tool versus alternatives like dedup_list or dedup_search. The context of '1-based index' implies usage when the index is known, but no when-not-to or alternative references are provided.

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