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

Annotations already declare readOnlyHint=true and destructiveHint=false, so "Read only." adds nothing and merely restates structured data. The description does add useful behavioral context that the return includes the credit balance alongside search status, but it says nothing about polling cadence, status values, or partial results.

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?

One front-loaded sentence covers both purposes with no padding. The trailing "Read only." is redundant with annotations and is the only wasted element.

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 one simple parameter and no output schema, the description should explain what the status payload looks like, but it does not describe possible status values or the shape of the credit balance. It is adequate for calling the tool, thin for interpreting the response.

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% and the single storeIds parameter is documented in the schema as "Store ids to check." The description never mentions storeIds or that a single call covers up to 300 stores, so it contributes no meaning beyond the schema; 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?

"Check the status of contact searches you started" gives a specific verb and resource, and it also names a second payload (credit balance). It is distinguishable from revealStores (which starts searches) and getRevealCost (which quotes price), though it never names those siblings explicitly.

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 "searches you started in the dashboard" implies a when-to-use context but is ambiguous about whether searches launched via revealStores are covered by this check. No explicit when-not or alternative routing is provided.

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