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

The read-only, idempotent, and non-destructive traits are already provided by annotations, so the description's added value is the exact-match requirement and the legalEntityType-is-unset nuance. This is meaningful behavioral context beyond the structured annotations, with no contradiction.

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?

The description is two sentences with no filler: the first states the operation and inputs, the second records a useful edge case. It is front-loaded 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 simple read tool with two fully documented parameters, rich annotations, and an output schema, this description provides the necessary selection criteria (single portfolio, exact identifier, settings/accounting policy) and a valuable unset-value detail. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, and both required parameters already carry 'exact name or slug' descriptions. The description mostly restates that matching mode and adds no new per-parameter constraints or formats, so the schema carries the semantic weight.

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 opens with a specific verb ('Read') and a clearly scoped resource ('one portfolio's settings and accounting policy'), then specifies the identifier type ('exact name or slug') and the included fields. This distinguishes it from list/balance/find siblings even without naming them, because it targets a single portfolio's administrative data.

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?

It clearly communicates the tool is for reading one portfolio's settings when an exact name or slug is known, which implicitly separates it from list/find tools. However, it does not explicitly name alternatives or state when not to use it, such as when balances are needed.

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