zen_structured_data

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

No annotations are provided, so the description carries the full burden. It states 'Extract', implying a read operation, but does not disclose any behavioral traits such as whether it waits for page load, handles missing data, or requires permissions. The lack of detail leaves ambiguity about side effects and prerequisites.

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 concise at one sentence, but it omits important context such as parameter usage and return format. While brevity is valued, the missing information reduces effectiveness. It could be improved by adding parameter and output details without excessive length.

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 no output schema, the description should explain what is returned (e.g., list of extracted objects, raw data). It provides no such information. The tool extracts structured data but does not clarify the return structure, leaving the agent uninformed about the response format.

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 description coverage is 0%, meaning the schema provides no parameter descriptions. The description does not mention the tab_id parameter at all, failing to add any meaning beyond the schema. The parameter remains underdocumented.

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?

The description clearly states what the tool does: extract JSON-LD blocks, OpenGraph, and Twitter card meta. It uses specific verbs and resource types, making the purpose clear. However, it does not specify that it operates on a specific tab (implied by tab_id parameter) or differentiate from sibling tools like zen_meta.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools such as zen_meta and zen_dom serve related purposes, but the description gives no context for when to choose this tool over others. No when-not or alternative references are present.

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