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

Adds real behavior beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false): validation happens before any write, failures return field-specific errors with no record created, and successful calls surface an identifier, reference number, web link, and non-blocking warnings. It stops short of stating permission requirements, duplicate-detection behavior, or idempotency, so it is strong but not exhaustive.

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?

Front-loaded with purpose, then behavior, then routing in three tight sentences. Slight redundancy between the opening clause about the 'registration template' and the closing sentence about the 'registration schema', which could be merged.

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 single-parameter but deeply nested mutation tool with annotations and an output schema, the description covers what it does, the atomic validate-then-create semantics, and the sibling boundary. It could still point at get_innovation_template as the way to obtain a valid payload shape, which is the main remaining gap.

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?

With one parameter and 100% schema coverage, the deep nested schema already documents every field, so the baseline is 3. The description contributes that the payload must match the 'current registration template' and the authoring version contract is implied by the schema, but it never names get_innovation_template as the source of that shape, so it adds only modest meaning.

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?

States a specific verb and resource ('Registers a new innovation in the user's Lightbringer organisation') plus the scope of input ('from a structured payload matching the current registration template'). It also names the sibling it is not (update_innovation), so an agent can separate creation from enrichment without opening a schema.

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?

Explicitly gives the when: 'capturing a concept that is not already recorded', and the when-not with the named alternative: 'enrichment of an existing innovation belongs in update_innovation'. It also carves out the downstream patent workflow ('without requesting patent preparation or filing'), which routes 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.