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

Goes well beyond the readOnly/destructive annotations by disclosing pagination mechanics (page/pageCount, up to 50 top-level members), that Client child lists are complete and not separately paginated, the meaning of direct=true, and the nullable Client reference. These are behavioral traits nothing else in the structured fields conveys.

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?

Four dense sentences, front-loaded with the core action and scoping. Every sentence carries distinct information, though the member/item taxonomy is packed tightly enough that it reads more like reference notes than prose.

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?

Despite an output schema existing (so return values need not be explained), the description still covers pagination, member taxonomy, and auth, leaving no gap an agent needs to call it correctly. Fully adequate for a 2-param read tool.

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 0%, so the description must carry the load: it explains that portfolioId comes from list_portfolios and that page is followed via returned page/pageCount. It does not restate the page bounds (exclusiveMinimum 0) but adds real meaning over the bare integer/string types.

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+resource ('Read one agency Account Portfolio') and keys it to the portfolioId sourced from list_portfolios, cleanly separating it from the sibling list tool. An agent can identify the operation without opening the 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?

Gives explicit workflow context ('Read before edits and after an uncertain write') and a precondition ('Account access required; no mutation or Scan'). It also points to list_portfolios as the id source, though it does not enumerate competing reads like get_client/get_site.

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