listClicks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds valuable context: cursor-based pagination, filtering constraints (silent-drop, derived-field unfilterability), and a detailed return structure. No contradiction with 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?

The description is well-structured with sections (Use when, Pagination, Filter/sort, See also, Returns) and bullet points. It is appropriately sized for a complex tool (~150 words) and front-loaded with the purpose and read-only hint. Could be slightly more concise in some filtering 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?

Given the absence of an output schema, the description explicitly states the return format. It covers pagination, filtering, and references external rules for operators. For a tool with 7 parameters and no output schema, this is fairly complete, though it relies on external rule documents.

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 100% (all 7 parameters have descriptions). The description adds meaning beyond schema by explaining usage (e.g., 'use next_page from previous response' for page, referencing filter operator rules). It provides context on how to use parameters effectively.

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 'List click records - Paginated enumeration of click records. Read-only.' It uses a specific verb ('list') and resource ('click records'), and distinguishes from the sibling tool 'getClick' (single record by ID).

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 explicitly says 'Use when: pulling click-tracking analytics for reports' and mentions filtering by user_id. It references pagination and filter rules. However, it does not explicitly state when not to use this tool or list alternative tools beyond getClick.

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