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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is covered. The description adds real value beyond that: validation runs before any record is created, invalid input yields field-specific errors with no partial record, and non-blocking warnings may accompany success. It does not mention permissions or rate limits, keeping it short of a 5.

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?

Five front-loaded sentences, each carrying distinct content (purpose, validation contract, alternative, patent scope, requirement). Dense and mostly waste-free, though the closing 'Requires a payload matching the current registration schema' slightly restates the opening clause.

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 complex nested-payload creation tool with an existing output schema, the description covers creation semantics, the atomic validation contract, the alternative tool, and scope exclusions. Nothing an agent needs to call it correctly is missing.

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?

The single payload parameter is fully documented in the schema (100% coverage), so the schema carries the field-level meaning. The description only adds that the payload must match the 'current registration template,' which is a mild versioning hint rather than substantive parameter guidance, matching the high-coverage baseline of 3.

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?

Opens with a specific verb (registers) and resource (innovation) scoped to the user's organisation and a structured payload. It explicitly distinguishes itself from update_innovation, so an agent can select it without opening sibling schemas.

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?

Gives an explicit when ('capturing a concept that is not already recorded') and when-not ('enrichment of an existing innovation belongs in update_innovation'), and it also carves out patent work ('without requesting patent preparation or filing'), routing the agent away from request_patent_preparation.

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