runToolSchemaValidation

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating no side effects. The description ('validate', 'diff') is consistent but adds no new behavioral traits beyond what annotations provide. No contradiction, but no extra transparency.

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?

Two sentences, front-loaded with the main purpose, no redundant information. Highly concise 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?

Despite the tool's complexity (3 parameters, nested objects, no output schema, no schema descriptions), the description is minimal. It fails to explain the critical target parameter or how the tool connects to a server, making it incomplete for an AI agent to use effectively.

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%, so the description must explain the three parameters (target, specVersion, expectedManifest). It does not mention any of them, leaving the AI agent without guidance on what 'target' (a complex union), 'specVersion', or 'expectedManifest' mean or how to use them. This is a critical gap.

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 clearly states the tool's purpose: validating that advertised tools have well-formed JSON-Schema inputSchema, with an optional diff against an expected manifest. The verb 'validate' and resource 'tool inputSchemas' are explicit, and it distinguishes from sibling tools like runJsonRpcCompliance or runSpecVersionAssertion.

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 primary use case is schema validation and mentions the optional diff feature. However, it does not provide explicit guidance on when to use this tool versus alternative siblings, nor does it state when not to use it. The context is clear but lacks exclusions.

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