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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable context beyond annotations by specifying what the template includes and that it provides capture guidance before drafting, giving the agent a clear expectation of the returned content. No contradiction with annotations.

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?

The description is a single, information-dense sentence that front-loads the core purpose and then expands with relevant details. Every clause contributes meaning—schema, per-field guidance, structure, and capture guidance—without redundancy or filler.

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 no parameters, a read-only annotation, and an output schema present, the description sufficiently explains what the tool does and what the template contains. An agent can select and call this tool without missing critical information; the only minor gap, explicit usage vs. alternatives, is not essential for a simple getter.

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?

There are zero parameters, so the baseline is 4 under the rubric; the description correctly avoids inventing parameter details. The description's content about what the template returns also helps the agent understand what the empty-input call will yield.

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 opens with a specific verb-resource pair, 'Returns the current invention authoring template,' and explicitly enumerates the template's contents: schema, per-field guidance, structure, and capture guidance. This clearly distinguishes it from siblings like get_invention (which returns an invention) and create_invention (which creates one).

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 'used to create a new invention' implies the intended use case, but there is no explicit statement of when to choose this tool over alternatives, nor any mention of when not to use it. Sibling differentiation is left to inference from the name and content.

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