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

Annotations already declare readOnlyHint and openWorldHint, and the description's "Read-only, free" largely restates that, though "free" adds the useful fact that no key or quota applies. It does not say what a negative result looks like (missing file vs. malformed content), whether both paths are tried, or whether redirects/HTTP errors are surfaced — meaningful gaps for a network probe.

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 sentence, front-loaded with the verb and scope, followed by the concrete probe targets and the safety/cost note. Nothing is redundant or padded.

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 read-only probe with full schema coverage and annotations, the description covers what is checked and the cost/safety profile. The only shortfall is the absence of any hint about the shape of the result (found/not-found, discovered endpoints), which an agent must infer since no output schema exists.

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 100% and the single param is documented as "Domain or https URL", so the schema does the work; the description adds nothing about accepted forms (bare domain vs. path vs. trailing slash). 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 (check) and a narrowly scoped resource (the x402 agent-readiness item), and names the exact well-known paths it probes (/.well-known/x402 and /.well-known/x402.json). This distinguishes it cleanly from the many sibling checkers (bursia_check_agents_json, bursia_check_llms_txt, bursia_check_mcp_discovery) without needing 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?

"Check one agent-readiness item" implies this is the single-item probe and that bursia_agent_readiness is the aggregate, but the alternative is never named and no when-not condition is given. An agent can infer the relationship but must guess rather than be routed.

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