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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions 'Requires auth', which is a real behavioral trait, but it does not explain what 'active' means, whether the tool returns all offers regardless of status, or what the response format looks like. This ambiguity could mislead an agent into expecting only non-terminal offers when the status parameter allows 'all'. Minimal disclosure beyond the auth requirement.

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?

The description is exceptionally concise: two short sentences that front-load the purpose and immediately mention the auth requirement. Every word is useful, and there is no redundant information. It meets the standard for appropriately sized, well-structured text.

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?

The tool is simple, but it lacks an output schema, so the description should clarify return values, default behavior, or pagination. It does not. Additionally, the 'active' term is left undefined, and the status parameter's role is not explained. For a read tool that returns a list of offers, the description is incomplete and could mislead.

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 0%, so the description must compensate for the lack of parameter documentation. It does not explain the 'limit' parameter or how 'status' interacts with 'active'. The enum values are self-explanatory to a degree, but the description's use of 'active' conflicts with the status enum (e.g., 'all'). The description adds no meaningful semantic value to the parameters; it may even cause confusion.

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 description clearly identifies the tool as a read operation for the user's own offers/bids ('View your active offers/bids'), using the verb 'view' and the resource 'offers/bids'. This distinguishes it from sibling tools like place_offer and withdraw_offer, which are mutations. However, the term 'active' creates ambiguity because the status parameter accepts 'all', and it's unclear whether 'active' means non-terminal statuses or is just a loose synonym for 'existing'.

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 states the target audience (your offers) and the auth requirement, giving clear context for when to use it. It does not explicitly mention alternatives or when not to use it, but the tool is self-explanatory among siblings as the primary 'view my offers' operation. Thus the usage guidance is implied rather than explicitly spelled out.

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