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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so safety is covered. The description adds non-obvious behavior: these are 'real prices' with enumerated entitlements, and crucially that payment is human-only on the claim page, meaning the agent cannot transact on the user's behalf.

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 dense sentence that front-loads the resource and then the tier list. The parenthetical bundle of entitlements is information-rich rather than filler, though the sentence is long enough to be slightly hard to scan.

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 parameters and an output schema exists, so return-shape detail is unnecessary. The description covers what the offers are, what each tier grants, and the human-payment constraint — enough for an agent to call it and use the result correctly.

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?

The tool takes zero parameters, so the schema carries no semantics to add. The description correctly spends its words on the returned offer structure instead.

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 resource (SaaSCity listing offers) and enumerates the concrete tiers it returns (free queue, Quick Pass, Premium) along with what each buys. It is clearly distinguishable from get_listing/search_listings, though it never names the sibling that would be the wrong choice.

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?

Usage is implied rather than stated: an agent is expected to call this to learn pricing/perks before or alongside submit_project. The line 'Only a human can pay, on the claim page' usefully bounds what the agent can do, but there is no explicit when-to-use, when-not-to-use, or alternative named.

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