ponisha_get_portfolio

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful output scope (contents with file ids, preview image, price range) and hints that omitting username targets your own account, but says nothing about auth requirements for private portfolios or error behavior for missing ids.

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 sentences, front-loaded with the verb and resource, and the dense field enumeration is all substantive. No filler or repetition of the tool name.

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 return-field enumeration is exactly what an agent needs to judge whether to call this instead of the list tool. Minor gaps remain: the provenance of portfolio_id and behavior for nonexistent or unauthorized portfolios.

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 0% with two parameters, so the description carries the burden: it does explain username semantics ('Leave username empty for your own'), which is genuinely valuable. However, portfolio_id gets no explanation of its source (presumably from ponisha_list_portfolio) or format, leaving half the parameters under-specified.

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?

The description opens with a specific verb and resource ('Get one portfolio item in full') and enumerates exactly what is returned (title, role, description, service type, skills, tags, contents, preview image, price range, duration). This distinguishes it in practice from the list/search/update siblings, though it never names those siblings explicitly.

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?

'Get one portfolio item in full' implies the detail-view use case versus ponisha_list_portfolio, but the description never states when to prefer this over alternatives or what to do when the item is not found or is private. The only explicit guidance is the parameter-level note 'Leave username empty for your own.'

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