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

With no annotations, the description carries the full burden for behavioral disclosure. It only states 'Detect and validate' without revealing fetch behavior, validation criteria, response format, or any side effects. This is minimal and leaves the agent guessing about what happens after invocation.

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, front-loaded sentence with no redundant words. It uses parallel verbs 'Detect and validate' and clearly states the object, making it efficient and well-structured.

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 simple tool with one parameter and no annotations or output schema, the description is adequate but not fully complete. It doesn't explain what 'validate' entails or what the tool returns, leaving some ambiguity. More detail about the validation process or return state would enhance completeness.

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 schema has one 'url' parameter with zero description coverage. The description mentions 'on a page', which hints at the parameter's purpose, but it doesn't explain URL handling or constraints beyond the schema's uri format. In this case, the single parameter is self-explanatory, so the description adds marginal value.

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 uses the specific verb 'Detect and validate' with a clear resource 'JSON-LD structured data on a page'. This distinguishes it from sibling SEO check tools that target content, meta, or performance, making the purpose highly clear.

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?

Usage is implied by the explicit mention of JSON-LD, but the description provides no explicit context for when to choose this tool over alternatives like seo_check_meta or seo_check_content. There are no stated exclusions or alternative references.

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