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

Annotations already cover readOnly/idempotent/destructive safety, so the description adds real value on top: the $0.20 USDC charge, the payment mechanism being required, and the important guarantee that unresolvable or ambiguous buyers are refused *before* payment, so the agent knows a failed call is free. Missing only output shape/size and latency expectations.

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, front-loaded with the price and then the payload contents, with the refusal behavior last. Appropriately sized for a paid bundle tool; the deliverable list is dense comma-clause prose that takes a second read but every item earns its place.

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?

No output schema exists, and the description compensates by enumerating the sections returned, plus the cost and the no-charge-on-refusal rule. What remains unstated is the response format (structured JSON vs prose) and whether renewal estimates are labeled as estimates — minor for a read-only paid brief.

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% — the allowed identifier forms (school:<URN>, trust:<UID>, org:<slug>, URN, exact name) and the x402 payment payload are fully documented in the schema. The description adds only the soft rule that ambiguous names are rejected rather than guessed, which is useful but does not extend parameter semantics much.

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?

Names a specific deliverable (a buyer brief) and enumerates its contents — hierarchy, edtech contracts and incumbents, renewals with windows, live tenders, trust changes, official links — scoped to exactly one buyer. That enumeration implicitly separates it from narrower siblings like school_renewals and school_signals_search, but no sibling is named explicitly.

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: it must be for a single resolvable buyer, and 'Unknown, ambiguous (candidates returned) or evidence-free buyers are refused before payment' tells the agent what inputs will fail. There is no explicit statement of when to pick this bundle over school_renewals or school_signals_search, nor a prerequisite check the agent should run first.

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