Get Unpublished Offer Report

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

Annotations already declare readOnlyHint=true, and the description confirms it is a read operation. It adds that the report contains 'all unpublished offers and reasons,' which is helpful. However, it does not disclose potential pagination, size limits, or whether the report is generated synchronously/asynchronously. With annotations, the bar is lower, but the description could provide more behavioral context.

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 concise sentences that immediately convey purpose and content. No extraneous words, front-loaded with the action and resource.

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?

Given the simplicity of the tool (one parameter, no output schema), the description covers basic purpose and content. However, it omits context such as the relationship to 'request_unpublished_offer_report', potential error states, or how to interpret the report output, leaving gaps for an agent unfamiliar with the process.

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 100%, and the description of the parameter ('The report ID from the unpublished offer report request') adds minimal meaning beyond the schema's own description. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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?

Description clearly states the tool retrieves an unpublished offer report by ID and specifies its content ('all unpublished offers and reasons'). The verb 'retrieve' is precise, and the resource 'unpublished offer report' is unambiguous, distinguishing it from sibling tools that retrieve other entities.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it should be used after obtaining a report ID, but does not reference the related tool 'request_unpublished_offer_report' or mention prerequisites. Usage context is left to the agent's inference.

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