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

Annotations say readOnlyHint=false, openWorldHint=true, idempotentHint=false – so this is a non-idempotent, open-world, non-read operation – yet the description calls it a 'screen' and a 'radar', framing it as observational. That framing is at odds with the write/non-idempotent annotation and is closer to an annotation contradiction than useful disclosure; there is no statement of side effects, cost, or repeat-call consequences.

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 sentences are appropriately short and the purpose line comes first, but the tagline in the title and the vague 'payout rail, escrow, deadline and zero-deposit conditions' list spend words without adding actionable information.

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 output schema exists, so the description must explain what a screening result looks like and how the caller should act on it – it does neither. With a non-idempotent, open-world annotation and an unconstrained nested input, the description is not sufficient for an agent to call this 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?

Schema coverage is 100%, but the single nested 'input' object is genuinely underspecified: additionalProperties is unconstrained and no keys are documented. The description adds only an example ({limit:20,rail:'base'}) without explaining what limit, rail, or any other accepted field means, so it fails to compensate for the nested-object ambiguity.

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 vague verb ('screen') plus a qualifying object, and adds a themed tagline ('fresh funded USDC work radar') that is marketing rather than specification. It is unclear whether this tool funds, screens, quotes, or purchases work; the sibling list contains many paid-* tools and this definition does not distinguish itself from execute_paid_product or paid_funding_rates.

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 when-to-use and no when-not-to-use guidance. It never names an alternative (e.g., paid_funding_rates, get_purchase_instructions) or a precondition for invoking it, so an agent cannot route between this and the many sibling tools.

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