get_tag_visits

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the key behavioral trait of filtering visits by a tag, which is useful context. However, it doesn't disclose pagination behavior, date filtering, or bot exclusion rules, which are relevant beyond the 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 a single, well-structured sentence that front-loads the primary action and scope. Every word contributes meaning, with no fluff or redundancy. It is appropriately concise for the core purpose.

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?

With six parameters, 0% schema coverage, and no output schema, the description is too sparse. It fails to mention filtering options (date range, bot exclusion) or pagination, leaving users without enough context to use the tool correctly. The read-only annotation helps but does not compensate for the missing parameter guidance.

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%, so the description must compensate. It implicitly covers the 'tag' parameter ('carrying a specific tag') but leaves the other five parameters (page, startDate, endDate, excludeBots, itemsPerPage) completely unexplained. The description adds minimal semantic value for most 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?

The description uses a specific verb ('List') and resource ('visits') with a clear scope ('short URLs carrying a specific tag'). This distinguishes it from siblings like get_short_url_visits (single URL) and get_domain_visits (domain-based). The action and target are 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 implies when to use this tool (when you need visits filtered by a tag) but provides no explicit exclusions or alternatives. It doesn't say 'use this instead of X' or specify prerequisites, so the guidance is only implied by the stated purpose.

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