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

Annotations already flag a destructive, idempotent, open-world write, and the description adds substantive context beyond them: it advances the description into the Lightbringer workflow, sends email notifications to specialist and submitter with the primary contact copied when applicable, and returns whether preparation was newly requested or already existed (consistent with idempotentHint). It also discloses a real limitation — email delivery status is not included — and defines what the call does NOT do, so there is no contradiction with destructiveHint.

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 the action and target, then the side effects, the return value, and the boundaries in a logical order with no filler sentences. The middle sentence is dense but each clause carries distinct information; a slightly tighter phrasing would reach a 5.

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?

An output schema exists, yet the description still summarises the meaningful return distinction (newly requested vs. already requested) and warns that email delivery status is absent. With prerequisites, side effects, and scope limits all stated, nothing an agent needs in order to call this 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?

Schema coverage is 100% for the single invention_id parameter, so the schema already carries the semantics. The description ties the call to 'an already registered innovation', which implicitly tells the agent what the identifier must reference, but adds no format or sourcing detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 ('Requests') and resource ('Lightbringer patent preparation') scoped to 'an already registered innovation', and explicitly separates itself from registration ('Separate from registration'). An agent can distinguish this from register_innovation or import_patent without opening the 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?

Gives a clear usage condition (innovation already registered, user has decided to pursue filing) plus explicit exclusions ('does not itself complete preparation, file a patent or pay for services'), which steers the agent away from wrong expectations. It does not name the specific sibling tools to use for those excluded steps, keeping it below a 5.

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