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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses the report contents (types found, parse failures, whether shopping-agent types are present) and implies a read-only parse, but says nothing about whether it fetches the live page, caching, permissions, or network failure behavior. Solid but incomplete for a tool with no annotation safety profile.

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?

Two tightly written sentences with no filler. The core behavior (what is parsed and reported) is front-loaded, and usage guidance follows immediately.

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 parameter, no annotations, and no output schema, the description does the heavy lifting by explaining what gets reported, which is important. It omits exclusions such as whether microdata/RDFa are ignored, but for a simple inspection tool it is nearly complete.

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 'url' parameter is already documented in the schema as the exact page URL to inspect. The description's page-type guidance (product vs homepage) adds light context but largely restates 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?

States a specific verb ('Parses') and resource ('every JSON-LD block on a page') plus the reported outputs, so the purpose is unmistakable. It does not name or explicitly contrast with siblings like check_agent_readiness, which likely also evaluates structured data, so sibling differentiation is only implicit.

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 concrete usage contexts – a product page to check Product/Offer markup, a homepage to check Organization/WebSite. It stops short of stating when not to use it or naming an alternative tool, but the context is clear enough to route an agent.

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