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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds only the useful 'free' cost signal and the list of probed paths. It says nothing about what a result looks like (found/not-found, HTTP status handling) or rate/timeout behavior for a network call.

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 that names the resource, the checked paths, and the safety/cost traits, with no filler. Every clause carries information an agent can act on.

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?

For a one-parameter, network-touching checker this is mostly sufficient, but with no output schema the description should indicate what the tool returns (e.g. whether the path exists / a boolean readiness result) and how failures are reported. That gap keeps it at minimum-viable.

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?

There is a single parameter at 100% schema coverage whose description ('Domain or https URL') already covers it, so the baseline is 4. The description adds that the target must be a public website, which slightly constrains the URL input beyond the schema.

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 resource ('Check one agent-readiness item on a public website') and then names the exact MCP discovery endpoints probed, which distinguishes it from sibling checkers like bursia_check_agents_json or bursia_check_agent_card without opening any 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?

The phrase 'one agent-readiness item' implies this is a single-check building block within the bursia suite, but the description never names when to use it versus bursia_agent_readiness or the other check_* siblings, nor any preconditions such as requiring a publicly reachable domain.

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