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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the response is fully structured and citation-bearing, which is real value, but says nothing about what happens on an unknown slug or how 'ranked' highlights are ordered/truncated.

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?

A single front-loaded sentence that packs the return contents without filler. It is efficient, though the extreme density means some of the listed payload elements are asserted rather than explained.

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?

An output schema exists, so return-value documentation is legitimately omitted, and the description's payload summary plus annotations cover the read-only contract. However, with a 0%-covered 5-parameter schema, the missing explanation of focusQuery and the visual-scaling flags leaves a real behavioral gap for an agent composing the call.

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 0% across five parameters, so the description carries the full burden. It only loosely gestures at three of them ('ranked visual highlights' for includeVisuals/maxVisuals, 'optional case-study signals' for includeCaseSignals) and never mentions focusQuery at all, nor defaults (5), bounds (1-8), or the visual-ranking semantics.

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 ('Returns full structured portfolio project data by slug') and enumerates the payload's distinctive contents (provenance, ranked visuals, case-study signals). An agent can distinguish it from list_portfolio_projects or get_project_followup_detail, though the description never explicitly names those alternatives.

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?

There is no guidance on when to reach for this tool versus the many sibling project tools (get_project_artwork_gallery, get_project_followup_detail, search_project_notes), nor any prerequisite such as where a valid slug comes from. Usage is only implied by the word 'slug'.

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