SmartProspect: review (re-sync) contacts for a filter

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

The description explicitly discloses that this modifies remote state (matching readOnlyHint=false), does not consume credits, and is blocked in readonly mode—valuable context beyond the annotations. It also clarifies it is not destructive, consistent with destructiveHint=false.

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?

All sentences carry useful information: purpose, safety profile, endpoint, and readonly restriction. No fluff or redundancy.

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 gives purpose, safety, endpoint, and a hint of return values while an output schema exists. It provides enough context for an agent to select and invoke correctly.

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 coverage is 100% and the filter_id parameter is already clearly described in the schema. The tool description mentions the filter context but adds no extra parameter meaning, so the baseline 3 applies.

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 states a specific action ('Re-sync contact metrics and statuses') on a specific resource ('contacts for a SmartProspect filter') and notes the returned counts. This clearly distinguishes it from sibling tools that search, fetch, or list contacts.

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 this is for re-syncing a filter's contacts but does not explicitly state when to prefer it over alternatives like search_contacts or fetch_contacts, nor does it describe exclusions beyond being blocked in readonly mode.

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