check_tracking

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

With no annotations provided, the description carries the full burden. It discloses the read-only nature ('Check', 'View') and the specific data returned (opens, clicks, replies), which is helpful. It does not mention output format, authentication, rate limits, or any other behavioral traits, but for a simple read tool this is acceptable.

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 two short sentences, front-loaded with the action, and every word adds value. There is no redundancy or unnecessary detail.

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 lack of an output schema and annotations, the description does not fully specify what the returned data looks like, how filters combine, or any prerequisites (e.g., emails must be sent). It is adequate for understanding the tool's purpose but not fully complete for an agent needing to predict behavior.

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 schema already documents all four filter parameters. The description adds no new meaning about the parameters; it merely confirms the tool surfaces tracking metrics. Thus a baseline of 3 is appropriate.

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 ('Check') and the resource ('email tracking status'), then specifics what it returns: opens, clicks, and replies. This distinguishes it from sibling tools focused on companies, contacts, and email generation/scheduling.

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 phrase 'for your outreach emails' gives some context for when to use the tool, implying it is for reviewing engagement on sent emails. However, it does not explicitly state when to prefer this over alternatives nor provide exclusions, so usage guidance is only implied.

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