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

Annotations only declare the safety profile (readOnly, idempotent, non-destructive). The description adds genuine data semantics beyond that: a failed check retains the last successful result, so absence of new records can only be concluded from a successful check, and subscription status is independent of delivery status. These are non-obvious staleness rules an agent could otherwise misreport.

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?

Four short sentences, front-loaded with what is read; each clause carries semantic weight. The only minor waste is re-enumerating returned fields that the output schema already covers.

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?

With an output schema present and annotations covering safety, the description's job is behavioral nuance, which it delivers via the failed-check and status-separation rules. It is complete enough to call correctly; only the missing explicit sibling routing keeps it from a 5.

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?

Only one parameter at 100% schema coverage; the schema already explains workflow_id is an account-owned ID returned by saved-search tools. The description's 'this account's' reinforces ownership but adds no syntax or format detail beyond the schema, so 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?

States a specific verb ('Read') and resource ('this account's saved-search updates') and enumerates the data returned: delivery revision, source dates, check times, downloads. It does not explicitly name the counterpart gisdb_set_lead_updates or distinguish itself from gisdb_get_search, so differentiation is inferable rather than stated.

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?

Usage is implied through interpretation rules (successful source check vs failed checks, subscription vs delivery status), but the description never says when to call this instead of siblings like gisdb_get_search, gisdb_list_saved_searches, or after gisdb_set_lead_updates.

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