list_accounts

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a safe read and the description discloses a dependency chain (view_id must come from list_views), but it says nothing about pagination defaults, result volume, or ordering behavior despite page/per_page/sort being accepted.

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?

Two short sentences with zero filler; the purpose comes first and the prerequisite second. Every clause 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 five-parameter list tool with no annotations and no output schema, the description covers the critical prerequisite but leaves pagination and ordering semantics unexplained. Adequate to invoke, incomplete to invoke well.

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 only 40%, so the description must compensate, and it does not: it only restates the view_id provenance that the schema already documents ('View id from list_views'). No meaning is added for page, per_page, sort, or sort_type.

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 ('List accounts (companies)') and scopes it with 'from a saved view', which is enough to distinguish it from sibling search_accounts. It stops short of explicitly contrasting the two, so it lands at clear-but-undifferentiated-from-siblings.

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 a concrete precondition: call list_views(module="sales_accounts") first to obtain the required view_id, which is genuinely actionable guidance. It does not say when to prefer this over search_accounts or when a saved view is the wrong choice, so no exclusions are covered.

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