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

With no annotations provided, the description carries the full burden and does well: it discloses webhook delivery over HTTPS, HMAC signatures, retries, 30-day duration, USDC pricing, and that UNKNOWN results are not charged. It still does not explain subscription lifecycle details such as renewal, cancellation, or what happens if the jurisdiction is not covered.

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 front-loaded with the core action and delivery mechanism, followed by pricing and verification claims. It is dense but reasonably structured; the accuracy and uptime statistics are somewhat promotional but still provide decision-relevant context.

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?

There is no output schema and no annotations, so the description should do more to explain what happens after the watch is created, how the subscription behaves, and what the agent should expect. It covers purpose, delivery, and price well, but leaves gaps around lifecycle, coverage prerequisites, and the label parameter.

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 adds meaning for keywords ('matching your keywords') and webhook_url (HTTPS webhook), but it does not explain the label parameter, jurisdiction format, keyword limits, or required status of parameters beyond what the schema already declares.

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 and resource: it watches a covered town for 30 days and delivers council/planning decisions matching keywords. It is clearly a subscription-style monitoring tool, but it does not explicitly distinguish itself from sibling tools such as watch_parcel or get_recent_decisions.

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 'covered town' implies that coverage must be checked and that this is town-level monitoring, but the description gives no explicit when-to-use guidance, exclusions, or alternatives. An agent must infer that check_coverage or list_coverage is a prerequisite and that watch_parcel is the parcel-level counterpart.

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