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

The annotations declare readOnlyHint=false, which is counterintuitive for a search-style tool; the description usefully explains this by noting results are 'Saved in the user's Puley history', and it discloses the source platforms and that output includes a reason and a link. It still leaves out practical traits such as result volume, credit/cost implications, and whether the history write is per-call or per-unique-result.

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 output shape and behavior are front-loaded in the first sentence, followed by compact parameter notes. The 'what:' / 'period:' label style is terse and slightly ungrammatical but wastes no words.

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 only two parameters and no output schema, the description needs to cover both inputs and the return shape, and it does: ranked posts with a buy-readiness rationale and a link, plus persistence to history. It stops short of stating result limits or pagination, but an agent can call it correctly from what is given.

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 'period' is an unconstrained string, so the description carries the load: it supplies the enum-like value set (day, week, month, year) that the schema omits, plus a clarifying example for 'what' (bookkeeping for freelancers). Minor gap: it doesn't specify how 'what' should be phrased or whether period bounds post date or the search window.

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 names the concrete resource (public posts on Reddit and X where someone asks for a recommendation) and the ordering principle (ranked by readiness to buy), which is far more specific than the vague title 'People asking for it'. It does not explicitly distinguish itself from lead-gen siblings such as find_leads or new_buyers, but the sourcing and intent-ranking make the scope unmistakable.

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 explicit when-to-use statement and no named alternative, even though several siblings (find_leads, new_buyers, search_posts) occupy adjacent territory. The agent must infer the use case from 'ranked by how ready they are to buy', which is implied guidance at best.

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