User profile

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by disclosing the returned facets (completed projects, rating, response rate, member since, last seen) and by drawing a hard scope boundary — private data such as contact and real name is not available. It does not cover error behavior for invalid or missing usernames, which keeps it below 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?

Two short paragraphs, front-loaded with the core purpose, then usage, payload, follow-ups and the privacy caveat. Every sentence carries distinct information; nothing is padded.

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 compensates by enumerating what the profile contains and what include_resume toggles, plus the privacy exclusion. For a two-parameter read-only lookup, an agent has everything needed to select and call it correctly.

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 both parameters are already fully documented, including the pattern for username and the default for include_resume. The description's notes on include_resume ('adds their work history') largely restate the schema, so baseline 3 applies.

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 a public Ponisha profile') and immediately scopes it to freelancer or employer, then enumerates the payload (level, skills, statistics, rating, activity). This is clearly distinguishable from sibling tools like pn_reviews or pn_user_projects, which surface only one slice of the same entity.

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?

Explicitly tells the agent where the required argument comes from ('a username from pn_search_freelancers, pn_bids or pn_project') and what to call next ('pn_reviews, pn_portfolios, pn_user_projects'). That is concrete routing in both directions, leaving little to inference.

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