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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered and the description correctly does not repeat it. It adds genuine behavioral context beyond the annotations by disclosing the payload composition (schema, per-field guidance, structure) and the intended capture workflow of interviewing versus authoring from existing material.

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?

It is a single front-loaded sentence that leads with the concrete resource returned and then layers in the capture-guidance detail. The em-dash clause ('interviewing an inventor who is present, or authoring from existing material') is dense but earns its place by describing the workflow the template supports; the sentence is borderline overloaded but not padded.

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?

With zero parameters, an output schema present, and annotations covering the safety profile, very little burden remains on the description, and it still explains both what comes back and how the guide is meant to be used. The only gap is that it never explicitly frames itself as the prerequisite step to register_innovation, which would make the workflow chain unambiguous.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on arguments.

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 names a specific verb and resource ('Returns the current innovation registration template') and enumerates its contents: schema, per-field guidance, structure, and capture guidance. It implicitly distinguishes itself from get_innovation (an actual record) and register_innovation (the write), but never names those siblings outright.

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?

Usage is only implied through the phrase 'before drafting' and the mention of interviewing an inventor or authoring from existing material, which hints at a pre-authoring step. There is no explicit statement such as 'call this before register_innovation' or any exclusion telling the agent when another template tool (get_company_context_template, get_strategy_template) is the right choice.

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