Project details

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description instead adds real operational context. It warns that include_bid_sample can take up to 30 s on bid-heavy projects and explains that finished projects expose accepted_price and done_by. Slightly short of a 5 only because it doesn't say what happens when the project_id is missing or invalid.

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 the core purpose, then the sequencing hint, then the less common option and sibling pointers. Dense but every clause carries information; the final sentence listing three siblings is the only slightly crowded part.

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, and the description does a solid job describing return fields including the conditional accepted_price/done_by for finished projects. Employer-block contents are named, though their exact shape is left to discovery.

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 covers only 50% (project_id is documented, include_bid_sample is bare). The description compensates well: it defines include_bid_sample as price statistics over the first 20 offers and flags the latency cost, which the schema does not convey. Still leaves the default behavior/format of that sample implicit.

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 ('Get one Ponisha project') and enumerates the returned payload: full description, budget, skills, deadline, employer track record. Distinguishes clearly from pn_search_projects, which returns many 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 explicit sequencing ('Use after pn_search_projects') and routes the agent to sibling tools by need: pn_bids for offers, pn_reviews for reviews, pn_user_projects for the employer's other projects. Conditions that select this tool versus alternatives are unambiguous.

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