list_accounts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions filtering and return fields but lacks details on permissions, rate limits, pagination behavior (beyond schema hints), or whether it's read-only. This is inadequate for a list tool with potential operational constraints.

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 concise and front-loaded, with two sentences that efficiently convey the core functionality and return data. Every sentence adds value without redundancy, making it easy to scan and understand.

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?

Given the tool's moderate complexity (list operation with filtering and pagination), no annotations, and no output schema, the description is minimally adequate. It covers what the tool does and returns but lacks behavioral context and usage guidance, leaving gaps for an AI agent to operate effectively.

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 100%, so the schema fully documents the four parameters. The description adds minimal value by mentioning 'filtering options,' which aligns with the 'filters' parameter but doesn't provide additional syntax or usage context beyond what the schema already states.

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 clearly states the tool's purpose: 'List accounts across all sources with filtering options.' It specifies the verb ('List'), resource ('accounts'), and scope ('across all sources'), though it doesn't explicitly differentiate from sibling tools like 'get_account' or 'list_identities' beyond the resource type.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions filtering options but doesn't specify scenarios, prerequisites, or exclusions, such as when to prefer 'get_account' for single accounts or 'search' for more complex queries.

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