Extract structured data (JSON-LD)

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

With annotations absent, the description discloses that it extracts all JSON-LD blocks, lists @type values, and returns parsed objects with parse errors. This covers core behavior but does not address edge cases like missing JSON-LD or dynamic rendering.

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?

The description is a single sentence that front-loads the action ('Extract every JSON-LD block') and then lists the outputs. No unnecessary words.

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?

Given the simple single-parameter tool and lack of output schema, the description adequately lists the return contents (parsed objects and errors). It could be more specific about the response structure, but it is sufficient for basic understanding.

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?

The only parameter 'url' has no description in the schema, and the description only indirectly refers to it via 'from a page'. It does not explain expected URL format, accessibility requirements, or how the URL is used beyond the general context.

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?

Description states 'Extract every JSON-LD block from a page' with a clear verb and resource, and distinguishes itself from sibling tools like extract_links and parse_sitemap by focusing on JSON-LD structured data extraction.

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 description implies the tool is for extracting JSON-LD structured data, but it does not explicitly state when to use it over alternative tools (e.g., extract_links for links). No exclusions or alternatives are mentioned.

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