serpwatcher_trackings

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

With no annotations, the description carries the full burden of behavioral disclosure. It states only a read-like action but does not mention pagination, response format, rate limits, or whether any query parameters are required, leaving the agent to guess.

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, front-loaded sentence with no filler. It efficiently conveys the core purpose, so it earns maximum points for conciseness even though other dimensions suffer from under-specification.

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?

For a list tool with no output schema and no annotations, the description is too sparse. It does not clarify whether query parameters are needed for pagination/filtering, what the response structure is, or how this endpoint relates to the broader SERPWatcher tool family, making it insufficient for correct invocation.

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's two parameters are generic body/query passthroughs with no tool-specific meaning, and the description adds no details about supported query parameters or filtering. Despite 100% schema description coverage, the coverage is boilerplate and does not explain how to shape a request to this endpoint.

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 ('Get') and resource ('SERPWatcher trackings'), and 'all' clearly indicates a list operation. It distinguishes from sibling detail/create/update/delete tracking tools, though it does not explicitly name an alternative.

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 guidance is provided on when to use this tool versus serpwatcher_tracking_detail or serpwatcher_tracking_stats. The phrase 'all trackings' implies a list scenario, but there are no explicit exclusions or alternative tool names.

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