serpwatcher_tracking_detail_legacy

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

No annotations are provided, so the description carries the full burden. It only says 'Get' and 'legacy endpoint', which implies a read-only operation but discloses no behavioral traits such as differences from the current endpoint, response format, rating limits, or authentication needs. The legacy aspect is mentioned but not explained.

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 zero waste. It clearly conveys the purpose and the legacy qualifier without fluff.

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?

The description is incomplete in the context of the sibling ecosystem. It fails to clarify what 'legacy' means behaviorally, when to use this over serpwatcher_tracking_detail, or any limitations of the legacy endpoint. No output schema is provided, so the description should fill more gaps, but it does not.

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%, so the baseline is 3. The description adds no parameter-specific information, but the schema already documents tracking_id, body, and query adequately. No compensation needed.

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 the action ('Get') and the resource ('SERPWatcher tracking detail'). The phrase 'using the legacy endpoint' explicitly distinguishes this tool from the sibling serpwatcher_tracking_detail (non-legacy), satisfying the sibling differentiation criterion.

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 an implied usage context: use this tool for the legacy endpoint. However, it does not explicitly state when to prefer this over the non-legacy alternative or any exclusions. No alternative tools are named, so guidance is minimal but not absent.

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