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

With annotations already supplying readOnly/openWorld/idempotent/destructive hints, the description still adds substantive behavior: authentication requirement, that the check is bounded and network-based, a five-minute cache window, no publication side effect, and rate limiting. These are exactly the operational traits an agent needs before calling a network-verification tool.

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?

Six short, telegraphic sentences with zero filler, front-loading the auth prerequisite and then layering constraints (scope, caching, no publication, rate limit). Every clause carries distinct information.

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?

An output schema exists, so return-value detail is unnecessary, and annotations cover the safety profile. Combined with auth, caching, rate-limit and no-publication disclosures, the definition gives an agent everything needed to invoke it 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 0% and officialUrl has no description in the schema, so the description carries the burden. It clarifies that the URL refers to the caller's public HTTPS site whose root homepage is inspected, which meaningfully disambiguates the single parameter, though it never states whether the input should be the bare origin or a full URL.

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 and object ('Check a visible anchor to https://shellwire.com/ on the root homepage of your public HTTPS site'), including the exact target URL and the required location. No sibling tool (fetch, search, submit_application) overlaps with this narrow verification task, and the agent can distinguish it without opening the schema.

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?

Gives the prerequisite (a verified builder Bearer token) and a key boundary ('No publication'), which implicitly separates it from submit_application. It does not explicitly state when in a workflow to run it or what to do on failure, so a 4 rather than a 5.

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