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

With no annotations, the description carries full burden and does well: it discloses irreversibility, the cascade destruction of holdings/transactions/balances under force, the blocking condition, and a confirmation requirement. It omits permission/auth requirements and rate limits, which is the remaining 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?

Three tightly packed sentences: core action first, then the flag semantics, then the safety warning and ID source. No filler and 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 destructive tool with no annotations and no output schema, the definition covers action, cascading effects, blocking condition, and irreversibility well. Missing only ancillary details like auth requirements or the effect on linked venture/transfer records.

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 the baseline is 3. The description's explanation of force largely mirrors the schema's own description, and 'Obtain portfolioId from get_portfolios' repeats the schema note, so it adds little meaning beyond the structured fields.

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 ('Permanently delete a portfolio') and immediately qualifies scope with the cascade behavior tied to the force flag. An agent can distinguish this from the sibling create_portfolio, update_portfolio, and get_portfolios without opening any 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?

Clearly explains the force/no-force decision ('Without force, deletion is blocked when the portfolio has any data') and prescribes a user confirmation step. It does not name a sibling alternative (e.g., a soft-archive path) for cases where deletion is undesirable, so it stops short of explicit when-not guidance.

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