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

Beyond the readOnly/destructive/openWorld annotations, it discloses page size (up to 50), sort order (by name), pagination flow, auth requirement ('Account access required'), and a non-obvious data trait ('Site counts deduplicate direct and inherited membership'). It also reinforces the read-only nature ('performs no mutation or Scan').

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 purpose, and every sentence carries informational weight (search scope, pagination, return fields, membership dedup). It is dense but not padded; a slight trim of the return-field sentence would tighten it.

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 paginated list tool with an output schema and read-only annotations, the description covers search scope, pagination mechanics, auth prerequisites, and notable return semantics. Nothing an agent needs to call 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 description coverage is 0%, so the description must carry the burden: it explains that 'search' matches name/description and that 'page' is a numbered page with page 1 as the omitted default. It stops short of covering the search maxLength or the page bound, but it adds substantial meaning beyond the bare integer/string 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 and resource ('Find agency Account Portfolios') plus the scoping mechanism ('by optional name/description search'). It is clearly distinguishable from sibling list tools such as list_clients or list_sites_and_topics 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?

Gives procedural guidance (omit page for page 1, follow page/pageCount) and notes that search is optional, which implies how to use it. However, it never names an alternative or a when-not condition (e.g., get_portfolio for a single portfolio), leaving tool selection to inference.

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