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

The readOnlyHint annotation already marks this as read-only. The description adds value by detailing what validations are performed (conflicts, circular dependencies, reserved names, parent_type correctness), which is beyond the annotation. It does not describe the return format, but for a validation tool this is a minor omission.

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 two sentences, front-loaded with the action and followed by specifics. Every word earns its place; there is no fluff or repetition.

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 validation tool with one parameter, a readOnly annotation, and no output schema, the description covers the essential aspects: what it does, what it checks, and when to use it. The only missing detail is the return value or error behavior, but that is not critical for an agent to decide when to call it. The distinction from build_validate (a sibling) is implicit via the 'schema' prefix and the description.

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 100% (the single parameter 'schemas' has a description). The tool description does not add further detail about the structure of each schema object, but the parameter name and description ('Array of schema definitions to validate') are self-explanatory. Baseline 3 is appropriate given full coverage.

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 states the specific verb 'validate', the resource 'schemas', and enumerates concrete checks (conflicts, circular dependencies, reserved names, parent_type correctness). It clearly distinguishes this from saving or updating schemas, and the name itself is unambiguous.

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 gives explicit timing guidance: 'Always validate before saving!' This tells an agent when to invoke the tool (before schema_save or schema_update). It does not explicitly name alternatives or exclusions, but the directive is clear and actionable.

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