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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description need not restate safety. It adds specific behavior beyond annotations by specifying that validation is performed against the authoring schema and that the response contains errors and warnings, which clarifies what kind of read-only operation this is.

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 states the action, target, and result without redundancy. It is front-loaded with the key verb and resource, making it easy for an agent to scan.

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 read-only validation tool with one parameter, a fully detailed schema, and an output schema present, the description is largely sufficient. It could be slightly more complete by explicitly saying to call it before submit_invention, but the schema and annotations carry most of the necessary context.

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 coverage is 100%, and the nested definition parameter is thoroughly described in the schema itself, so the description does not need to document fields. The description merely calls the object a 'draft invention,' which aligns with the schema but adds no material semantic value beyond it.

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 a specific verb ('Validates') and a clearly defined resource ('a draft invention against the authoring schema'), and names the result (errors and warnings). It is clearly distinct from creation, retrieval, and submission siblings, but it does not explicitly name or contrast any alternative tool, so it stops short of a 5.

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 phrase 'draft invention' implies this is a pre-submission/pre-publication check, and the validation-against-schema wording implies it is for compliance checking. However, the description gives no explicit when-to-use or when-not-to-use guidance and names no alternative tools such as submit_invention or create_invention.

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