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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is covered structurally. The description adds non-obvious context beyond them: an authorization requirement (owner or org.portfolio.manage) and a plan-tier gate (BUSINESS+). It does not explain what 'destructive' means here (overwriting prior name/description), leaving a small gap.

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, purpose front-loaded before the permission caveat, with no filler. The '(BUSINESS+ feature)' parenthetical is slightly cryptic but compact enough to be worth its space.

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 and full schema coverage, the definition needs mainly to establish purpose, auth, and plan gating, all of which it does. It omits a minor edge case: only portfolioId is required, so behavior when neither name nor description is supplied (no-op vs. error) is unstated.

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 portfolioId, name, and description are all self-documented (including the 2-char minimum on name). The description only restates that name/description are the updatable fields and adds no format or constraint detail, 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 (update) and resource (portfolio) plus the exact mutable fields (name, description), so it is clearly distinct from create_portfolio, get_portfolio, and update_project. It does not explicitly name a sibling alternative, which keeps it from a 5.

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 concrete preconditions for use: the caller must be the portfolio owner or hold org.portfolio.manage, and the operation is gated behind the BUSINESS+ tier. No when-not-to-use case or alternative tool is named (e.g., what to use for members or projects in a portfolio), so it falls short of a 5.

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