Project bids

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

Beyond the readOnly/idempotent annotations, it discloses performance behavior (about 3 s, up to 30 s on 100+ bid projects) and the operational response to it (keep limit small, page through). It also states the currency unit (Toman), which is not inferable from any structured field.

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?

Three tight sentences, front-loaded with what you get, then why to call it, then the performance caveat. Every sentence carries information the schema and annotations do not.

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 steps in and names the returned fields and their cross-reference (bidder names link to pn_profile). Combined with the latency warning and unit disclosure, an agent has everything needed to call this correctly and interpret results.

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%, so the schema already defines all three parameters; the description adds real guidance by tying `limit` to the slow-response constraint and directing paging via `page`. It doesn't clarify the page/limit interaction at max values, so it sits just above baseline rather than at the top.

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?

Opens with a specific verb+resource: 'List the offers freelancers made on a Ponisha project,' and enumerates the returned fields (price, days, pitch, bidder track record). This is clearly distinguishable from siblings like pn_project (project detail) and pn_search_projects (finding projects).

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 two concrete use cases: 'see the competition on a project before bidding' and 'compare bidders.' It also routes the agent to pn_profile for bidder detail rather than doing that work here. It stops short of explicit when-not-to-use guidance or naming a competing sibling outright.

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