Remove Portfolio Item

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

Annotations already convey destructiveHint and readOnly=false, but the description adds important nuance: the project itself is not deleted, only the portfolio association. It also discloses the return behavior (success message), which is valuable given no output schema.

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 concise sentences, front-loaded with the primary action, followed by a clarifying caveat. Every word contributes meaning; there is no redundancy.

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 two-parameter mutation, the description covers the action, non-destructive scope, and return type. Combined with complete schema and annotations, it provides sufficient context. Minor gaps: no mention of error cases or effects on ordering within the portfolio.

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 provides 100% coverage for both parameters, including types and format examples. The description adds no additional parameter detail beyond restating the overall action, so it does not exceed the schema baseline.

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 the action: 'Remove a project from a portfolio.' It further distinguishes itself from deletion tools by noting 'This does NOT delete the project — it only removes the association,' which separates it from asana_delete_project and asana_delete_portfolio.

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?

Provides clear context for when to use it (removing a project from a portfolio) and an explicit when-not-to-use (not for deleting the project). It does not name alternatives, but the exclusion is specific enough to guide selection.

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