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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no pagination, result limits, ordering, auth requirements, or response shape. Only the read-only nature is implicitly conveyed by the verb 'List'.

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?

One short, front-loaded sentence with zero wasted words. It is efficient, though the brevity comes at the cost of substance covered in other dimensions rather than being tight prose.

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 annotations, no output schema, and an undocumented parameter mean the description is the only source of context, and it delivers a single clause. For a discovery/listing tool an agent needs to know result scope and filtering behavior, neither of which is here.

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 0%, so the description must explain the single parameter, and it only echoes the field name ('filtered by capability'). It does not say whether the value is an exact match, an identifier versus a label, or case-sensitive, leaving nothing beyond the bare 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?

States a specific verb and resource ('List capability offers') plus the filtering dimension, so the operation is unambiguous. It does not differentiate itself from nearby siblings such as list_needs, get_opportunities, or publish_offer, which forces the agent to infer the boundary.

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 gives no explicit when-to-use guidance and never names an alternative. The words 'optionally filtered' only tell the agent the filter is optional, not when to apply it or when to reach for a sibling tool instead.

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