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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it adds real behavioral context: the required permission scope and, importantly, that a duplicate add returns an error so callers can detect duplicates. This is consistent with idempotentHint=false. It omits reversibility (whether/how membership can be removed) and invalid-id behavior.

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?

Three compact clauses: action, permission gate, duplicate behavior. No filler, and the purpose is front-loaded. The "(BUSINESS+ feature)" and permission abbreviations add density but earn their place as gating information.

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 2-param mutation with no output schema, the description covers purpose, authorization, and the notable duplicate-error behavior, which is enough to call it correctly. It could still say what the successful response contains and how to undo the membership.

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 portfolioId and projectId are already documented as ids in the schema. The description adds no parameter-level detail (formats, cross-references, constraints), so the 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+resource pair ("Add a project to a portfolio"), which is unambiguous and distinct from sibling add_project_member, create_portfolio, and update_portfolio. It does not explicitly name or contrast with any alternative tool, so it stops short of the top score despite the clear operation.

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 gives a gating prerequisite (requires org.portfolio.manage, default Manager+, BUSINESS+ feature) but no when-to-use/when-not guidance or named alternative for adding membership. Usage is implied by the operation name rather than stated, making this minimum viable.

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