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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value on top: newest-first ordering, cursor-based pagination (pass next_cursor back as cursor), and the auth requirement (Cotlet API key with access to this app).

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?

Front-loaded with what is returned, then filtering, then pagination, then auth. Efficient overall, though 'newest first' is stated twice and the subject 'projects' is restated several times, so a small trim is possible.

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, the description carries the return-shape burden and does so — item fields, ordering, pagination mechanics, the get_project follow-up, and the required API key are all present. An agent has everything needed to call it correctly and consume the response.

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 100%, so the baseline is 3. The description goes beyond it by explaining the cursor parameter's provenance and lifecycle ('Pass next_cursor back as cursor for the next page'), which is the key detail the schema alone cannot convey since there is no output schema declaring next_cursor.

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 (search) and resource (projects buyers posted) plus the exact fields returned (title, budget, category, proposal count). It also distinguishes itself from get_project by noting that get_project returns the full brief, so the agent can tell the two apart without opening a schema.

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?

Gives concrete usage context: filter by keyword, or by posting time 'to read only what came in since your last check', and route to get_project for the full brief. It names the alternative tool and a selection condition, but stops short of explicit when-not-to-use exclusions (e.g. relationship to list_proposals).

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