analytics_period_duplicates

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

Annotations already declare readOnlyHint and openWorldHint. The description adds a prerequisite step but does not disclose additional behavioral traits like rate limits, data freshness, or error handling. Without annotations, this would be a 2, but with them, the description is adequate but not exceptional.

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 concise (three lines) and well-structured with clear sections for purpose, prerequisite, usage, and trigger words. Every sentence adds value without redundancy.

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 the tool's simplicity (one parameter, no output schema), the description covers the essential aspects: what it does, prerequisite, and when to use. It does not describe return format or error behavior, but these are not critical given the lack of output schema.

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?

The schema has a single required 'period' parameter with 0% description coverage. The description adds context by linking 'period' to a statement period and recommending calling analytics_periods_list to get valid values, which compensates for the schema gap.

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 row hash groups for a statement period,' using a specific verb and resource. It distinguishes this tool from siblings like analytics_range_duplicates and other analytics_period_* tools by focusing on duplicates within a single period.

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 provides explicit prerequisite guidance ('Before calling: Call analytics_periods_list first') and defines when to use with trigger words. It does not explicitly exclude cases but provides sufficient context for correct invocation.

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