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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description need not restate it. The description adds content-level context about what the returned list contains, which is useful, but discloses no additional behavioral traits such as ordering, pagination, or completeness guarantees. 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?

A single front-loaded sentence that states the core purpose first and then elaborates with concrete examples. The example enumeration adds a little length but earns its place by setting expectations for what counts as a 'framework' in this library. No fluff.

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?

Complete for a zero-parameter, read-only list tool: the output schema covers the return shape, annotations cover safety and idempotency, and the description explains exactly what the list contains. Nothing an agent needs to call it 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?

The tool has zero parameters, so per the rubric the baseline is 4; there is nothing for the description to document. Schema coverage is trivially 100% with an empty object.

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 (list) and a precise resource (frameworks published by The Revenue AI Report), then disambiguates the scope by naming both the canonical concepts (Proof Gap, Optimization Theater, Reversal Ledger, Eight Seat Read) and the named operating frameworks (SCALE, OAR, LOPAFT, L1–L6 Maturity Ladder). An agent can tell exactly what this returns and how it differs from the get_framework sibling.

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 makes clear what content is included, which implies a browse-overview use case, but it never explicitly states when to prefer this over get_framework for a single framework, nor names any alternative. Usage context is implied by the list-vs-get sibling pattern rather than stated.

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