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

The description goes well beyond the minimal annotations by disclosing that repeated calls return identical content, that each call appends a usage-counter row, and that a fresh invocation_id is returned for feedback. These are meaningful behavioral side effects and idempotency details an agent needs before invoking.

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 sentences, with the primary purpose in the first sentence and behavioral caveats in the next two. Every sentence adds non-redundant information, and the most decision-relevant fact (same content on repeat calls) is placed prominently.

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?

Given the presence of an output schema and annotations, the description covers the non-obvious operational details: stable content across calls, side-effect cost, and invocation_id semantics. Nothing critical for selecting or invoking the tool 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%, with each parameter already described in the input schema, so the baseline is 3. The description adds no further parameter-level detail; it focuses on the return payload rather than clarifying loop_slug, node, or context beyond what the schema states.

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 ('Returns') and identifies a concrete resource ('a chapter's published framework text'), then enumerates exactly what that text contains (modes, questions, output format). This makes the tool's function clear and distinct from the generic get_chapter sibling, even without an explicit comparison.

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 description explains the intended use: the returned framework is 'reference material for the assistant to apply as it judges appropriate.' It gives clear context for when to call the tool, though it does not explicitly name alternative tools or exclusion conditions, stopping short of a 5.

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