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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds no behavioral context of its own — nothing about pagination, volume of results, or what an "offering" record contains. The "ERP title comes from configuration" line is opaque and gives the agent no actionable information.

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?

Only two sentences, but the second is unexplained noise and the first buries the core purpose behind an awkward "footnote of small demonstrations" clause. Front-loading is weak and the wording would need trimming rather than expanding.

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?

An output schema exists, so return values need not be described, and annotations cover safety. Still, the definition leaves the central concept (what an "offering" is) and the filter's effect undefined, which is not enough for an agent to decide reliably whether to call it.

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?

With a single optional parameter at 100% schema description coverage, the schema already documents the category filter, so the baseline of 3 applies. The description never mentions the category parameter or what values it accepts, so it contributes nothing beyond the schema.

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 verb+resource ("Lists EAC Partners offerings") is identifiable, but "offerings" is never defined and the qualifier "including a footnote of small demonstrations built by EAC Partners" muddies rather than sharpens scope. The closing sentence ("The ERP title comes from configuration") describes an unrelated implementation detail. No sibling tool covers offerings, so differentiation is implicit at best.

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?

There is no statement of when to call this tool, when not to, or which sibling (e.g. match_need, list_subscriptions) to prefer for adjacent needs. The only usable cue is the optional category filter, which is implied rather than explained.

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