Generate JSON-LD schema

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

Annotations already provide readOnlyHint and openWorldHint. Description adds 'Returns valid JSON-LD' and 'ready-to-paste' but does not elaborate on behavioral aspects like error handling, latency, or required network access. Adequate given annotation coverage.

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?

Three sentences, each serving a clear purpose: purpose, usage guidance, output guarantee. No fluff, front-loaded with the main action.

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?

Tool has only two parameters and no output schema. Description sufficiently explains output type ('valid JSON-LD') and use cases. Slightly lacking in detail about output format (e.g., code block) but still largely 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 covers 100% of parameters with descriptions. Description adds context ('tailored', 'auto-detect') but does not add meaning beyond the schema. Baseline score 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?

Description specifies verb 'Generate', resource 'JSON-LD schema', and purpose 'tailored to a website to improve understanding by AI and search engines'. Clearly distinguishes from sibling tools (e.g., tracking, auditing, visibility).

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?

Explicitly states when to use: 'when someone asks for schema, structured data, JSON-LD, or wants actual markup.' While it does not list alternatives, the sibling tools cover different use cases, so no confusion.

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