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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: an ownership requirement on the report and an explicit rule that missing images and historical answers must not be invented or regenerated — a constraint an agent would otherwise violate. It does not describe response shape or what an empty/missing section looks like.

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?

Three short sentences, front-loaded with the action and content scope, followed by the precondition and the constraint. No filler; the only cost is that the section enumeration and the no-invention rule are packed tightly without connective explanation.

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 read-only tool with two parameters and no output schema, the description covers what is returned (section content types), the access precondition, and the integrity constraint. The notable remaining gap is that without an output schema, nothing tells the agent the shape of a returned section or how a missing section is signalled.

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 0%, and while sectionId's enum values are partly echoed in the description (palette, hair, best-version, plan), the mapping is loose and most of the 15 enum values are unspecified. orderId is only obliquely explained via 'requires an owned report'; the description never says the ID refers to the report/order, which is exactly the missing semantic.

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 ('Read') and resource ('a selected saved section') and enumerates representative section content (palette, style, hair, Best Version, plan), which lets an agent distinguish this from the broader get_report sibling. It stops short of naming get_report directly, so differentiation is inferred rather than stated.

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?

'Requires an owned report' gives one hard precondition, and the section list implies this is the single-section alternative to fetching a whole report. There is no explicit 'use this instead of get_report when...' routing and no guidance on error behavior when the report is not owned.

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