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 fully covered. The description adds only the scope of the returned set (your outgoing offers plus offers on your listings), which is modest added context; it says nothing about ordering, pagination, or whether expired offers appear. Adequate but not rich beyond the 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?

Very short and front-loaded, with the WHEN clause and sibling contrast arriving immediately. The redundant name prefix and the example call are low-value filler, but total length stays well within budget.

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?

With an output schema present and full annotation coverage, the description does not need to explain return values or safety. It covers scope, trigger, and alternative, which is enough for a zero-required-parameter read tool; only edge cases like empty-state behavior are unmentioned.

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?

Single optional parameter ('key') with 100% schema description coverage, so the schema already explains it as an arena key or Authorization bearer alternative. The description's 'Example: bazaar_check_my_offers {}' only signals that no arguments are required, adding minimal meaning beyond the empty required array. Baseline 3 applies when the schema carries the load.

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: seeing 'offers you made and offers on your listings', which is a precise, personal-scope read. It names a sibling (bazaar_browse_listings) as the contrasting public board. The leading repetition of the tool name is dead weight and the closest behavioral alternatives (booth_feed, bazaar_resolve_proposal) are not addressed, so it stops short of a 5.

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?

Explicit 'WHEN:' clause gives the trigger condition, and 'Differs from bazaar_browse_listings (public open board)' supplies a clear contrast with an alternative. It does not say when *not* to use it or which tool to use for acting on the offers shown (e.g. booth_accept/decline, bazaar_resolve_proposal), so it is clear but not exhaustive.

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