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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds blast-radius detail the annotations cannot express: deletion is scoped to the grouping and does not cascade to member projects, and no external provider call or credit spend occurs. It does not cover permissions or error 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 short sentences, zero filler, with the core action front-loaded and the side-effect and cost caveats following in priority order. Every sentence earns its place.

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 single-parameter destructive tool with no output schema, the definition covers action, blast radius, idempotency context, and cost. Only permission requirements and failure modes are unaddressed, which is a minor gap on a tool whose annotations already mark it destructive.

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?

One parameter with 100% schema description coverage, and the schema already tells the agent to use list_portfolios to find the ID. The description adds nothing about the portfolioId itself, so this is the baseline 3.

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 ('Deletes a portfolio') and immediately disambiguates it from the similarly named remove_portfolio_projects by clarifying that member projects are untouched and only the grouping is removed. An agent can pick between the two without opening either schema.

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?

Cost guidance is explicit ('no SEO data provider is called and no credits are spent'), which is real usage signal in a toolset full of credit-consuming calls, but there is no explicit when-to-use/when-not or named alternative tool. The routing to remove_portfolio_projects is only implied by the 'member projects untouched' clause.

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