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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive behavior beyond them: fuzzy-match priority order (chosen niches, then bio and Rates; city/country, then bio), cross-currency comparison for max_from_price, and the silent exclusion of price-on-request creators. It stops short of stating page size or result ordering, which keeps it from a 5.

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?

Four dense sentences, front-loaded with purpose, then filter semantics, then the exclusion edge case, then the pagination contract. Nothing is repeated from the schema and no sentence is filler.

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 5-param search tool with no output schema, the description covers filtering, edge cases, and how to page. The one remaining gap is that it never indicates what a creator result contains, though the pagination hint partially offsets the absent output schema.

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?

At 60% schema coverage the description meaningfully compensates: it explains where 'niche' and 'location' are matched, that max_from_price is a starting price converted into the creator's currency, and that cursor is the previous response's next_cursor. Only 'platform' gets no meaning beyond the schema's 'Platform of the Rate'.

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 specific verb and resource ('Find creators with a live Piku page') and enumerates the exact facets it searches on: niche words, location, platform, and starting price. The 'live Piku page' qualifier scopes the result set precisely, so an agent knows exactly what population this returns.

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 scope statement plus the pagination contract ('pass next_cursor back as cursor') make clear this is an iterative search/list tool, and the max_from_price exclusion rule tells the agent when a filter silently narrows results. No sibling alternative is named, but none of the listed siblings offers creator search, so there is no real ambiguity to resolve.

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