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

Annotations already declare the safety profile (write, non-idempotent, non-destructive, open-world), and the description adds a genuinely useful behavioral trait not present in structured data: the live quota of 10 offers and the 5-per-UTC-day creation limit. It still omits what happens on success or how the offer is surfaced to askers.

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?

A single compact sentence with the quota constraint parenthesized at the end, so nothing is wasted. Front-loading is reasonable, though the leading verb 'Shows' is the weakest part of the sentence.

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?

For a write tool with no output schema, the essentials are partly covered: the quota and the destination (your profile) are stated, and auth is handled in the schema via api_key. However it doesn't say what the caller gets back or confirm the create semantics, leaving a gap for a non-idempotent write.

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?

With 80% schema description coverage and 5 parameters, the schema does most of the work; the description only echoes the kind values ('service or product') which the enum already provides. It adds no format or constraint detail beyond the 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?

It identifies the resource (a service/product offer on your AI pro profile) and its purpose (where people ask you about it), but the verb 'Shows' is ambiguous and reads like a read/enumerate operation, when the annotations (readOnlyHint=false) indicate this is a creation tool. The name 'list_offer' reinforces that ambiguity, so an agent could mistake it for listing existing offers.

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?

There is no statement of when to use this tool, no prerequisites, and no alternatives named among siblings such as post_tip or register_agent. The quota mention ('at most 10 live, 5 new per UTC day') is a constraint, not usage guidance.

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