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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds a meaningful extra constraint: offers are funded and legitimate, and the user must complete human actions truthfully, which is useful context beyond the annotations. It does not discuss return format, result size, or any call-specific side effects.

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 short sentences deliver the core purpose and the most important usage constraint without filler or redundancy. The key information is front-loaded in the first 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?

There is no output schema and the description does not say what the tool returns, how results should be presented, or how the four parameters affect the search. Given the sibling tools include get_earning_options and start_agent_earn, the description leaves important selection and invocation context unclear.

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% and the description does not mention device, country, account_handle, or zero_spend_only. There is no parameter-level meaning to help an agent decide how to set these values, so the description entirely fails to compensate for the schema's missing documentation.

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 operation as finding offers and adds specific qualifiers ('funded legitimate human-required') beyond the title, so an agent can tell this is about user-performed paid opportunities rather than automated earning. It does not explicitly name or compare against sibling tools, so it stops short of full differentiation.

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 phrase 'human-required' and the warning that 'human actions must be completed truthfully by the user' imply this tool should be used when a real person will manually complete offers, not when using automated agents. However, no alternatives are named and no explicit when-to-use or when-not-to-use conditions are provided.

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