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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description adds that output is markdown-formatted with named sections, which is real context beyond the annotations. It stops short of anything about size, truncation or the shape of the illustrated variant beyond the section name.

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?

Two sentences, the output shape first and the optional flag second, with no filler. The conditional is clearly signposted with "With include_illustrations", so the agent can parse the branch at a glance. Slightly dense phrasing in the second sentence is the only friction.

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 an output schema present, the description does not need to enumerate return fields, and it still names the salient ones. For a two-parameter read-only tool the definition covers the important ground; the missing piece is routing guidance against get_innovation_template and list_innovations.

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 description coverage is 100%, so both parameters are already documented, and the baseline of 3 applies. The description reinforces the conditional behavior of include_illustrations and adds a nuance the schema only hints at (drawings it suggests preparing), but it offers no format or constraint detail for invention_id beyond the schema's pattern and length rules.

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 and resource ("Returns an innovation record") and enumerates its contents: problem, solution, technical details, prior art, and markdown rendering. That is enough to separate it from list_innovations, but it never names the sibling it is not (e.g. get_innovation_template) or says which one to pick for a template versus a record.

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: an agent infers this is the fetch-single-record call from the verb and the required invention_id. The only explicit guidance is attached to include_illustrations ("for example to check what is there before uploading"), which is useful but scoped to one parameter. Nothing states when to prefer this over list_innovations or get_innovation_template.

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