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

Goes well beyond the annotations: omission preserves saved fields, explicit null clears the description, blank normalizes to null, name cannot be cleared, edits are atomic and preserve omitted fields under concurrency, requires Account access, and advises re-reading after uncertainty. This is rich operational context for a destructiveHint=true mutation.

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?

Front-loaded with the operation, then constraints, then guidance — well organized. It is dense and semicolon-heavy, packing many clauses into few sentences, but nearly every clause conveys non-obvious behavior rather than filler.

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?

An output schema exists, so return values need not be described, and the description covers everything else an agent needs: validation rules, clearing semantics, atomicity, access requirements, and the boundary against sibling membership tools.

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?

With 0% schema description coverage, the description carries the full burden and delivers: name must be nonblank, Account-unique, and non-clearable; description accepts null to clear and normalizes blanks; portfolioId is the lookup key. This meaningfully exceeds the terse type/format constraints in the schema.

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 (Edit) and resource (agency Account Portfolio name and/or description) with the key identifier (portfolioId). It distinguishes itself from siblings by explicitly routing membership changes to the separate add/remove tools.

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 explicit prerequisites ('Read get_portfolio first'), explicit alternative routing ('Membership changes use the separate add/remove tools'), and explicit constraints ('At least one supplied edit is required'). An agent knows when to use this and when not to.

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