Show Project

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, which cover the safety profile. The description adds that it returns a JSON object describing the requested records, but does not elaborate on the structure or any additional behaviors like pagination (despite page/per_page params).

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?

The description is four sentences and provides key information. It is somewhat repetitive (twice mentions 'Portfolio records') and includes optional API endpoint details. It could be slightly more concise but is not overly verbose.

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?

For a simple show endpoint without an output schema, the description could better describe the return structure. It says 'full details' and 'JSON object', but lacks specifics on what fields are included. The mislabel of 'Portfolio records' also reduces completeness.

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?

The input schema has 100% coverage, so the description does not need to repeat parameter details. It mentions required parameters (id, company_id) but adds no new meaning beyond the schema. The view, page, and per_page parameters are not discussed.

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 clearly states it fetches full details of a specific project, but uses 'Portfolio records' inconsistently. It distinguishes from list operations by specifying a single project, but does not explicitly contrast with other show tools.

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?

The description indicates this tool is for fetching full details of a specific project by identifier and mentions required parameters. However, it does not provide guidance on when not to use it or suggest alternatives like list_projects for overviews.

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