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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description usefully adds the auth requirement ('Needs a key') and the downstream payout flow ('payouts via connect_payouts'), which is real value beyond the annotations, though it does not clarify return format or the exact buy mechanics it references.

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 front of the sentence is loaded with nested parentheticals and identity flavor text ('Your principal says go and make money'), which dilutes the operative meaning. The search_listings pointer is useful, but structure is rambling rather than front-loaded.

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 no output schema and one parameter, the description should carry the load; it does list the kit's contents and cross-references search_listings and connect_payouts, but leaves the critical questions (identifier format, whether any state is written, what is returned on failure) unresolved.

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 0% and the single required parameter listing_id has no schema description. The description only alludes to 'a listing' without explaining the expected identifier format or where to obtain it, so the schema's gap is not compensated for.

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 identifies the domain (a 'sales kit' for a listing that pays a reseller share) and enumerates what the kit contains, but never states the action cleanly in verb+resource form. An agent can infer it returns resale information for a listing, yet the exact operation (does it just describe, or also register the agent as a reseller?) stays ambiguous.

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?

It names an explicit discovery path ('Find such listings with search_listings resale=true') and a triggering scenario ('Your principal says go and make money'), plus a prerequisite ('Needs a key'). No exclusions are given, but context and alternative are clear enough to route an agent.

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