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

With no annotations, the description carries the burden. It discloses that no provider call is made, which is a key behavioral trait. However, it does not mention side effects, output format, or permissions needed.

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?

A single sentence that starts with the verb 'Plan', directly stating the tool's action. No filler or redundancy.

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?

Despite good purpose clarity, the description omits what the plan output looks like, prerequisites, and how to use the result. With 7 parameters and no output schema, the agent lacks sufficient context for correct usage.

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 low (43%). The description only hints at 'URL or markdown' mapping to url and page_markdown parameters, but does not explain sync, target, keyword, page_type, include_jsonld. Many parameters lack 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?

The description clearly states the tool plans JSON-LD schema for a URL or markdown page, with the specific verb 'Plan' and resource 'JSON-LD schema'. It distinguishes from siblings like agentseo_content_brief which create briefs.

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 usage via 'without a provider call', suggesting local operation, but does not explicitly state when to use this versus other content tools (e.g., brief, outline). No when-not or alternatives given.

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