brc_list_accounts

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

No annotations are provided. The description only states the action without disclosing any behavioral traits such as whether it is read-only, pagination behavior, authentication requirements, or side effects.

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?

While the description is short (4 words), it is too sparse for a tool with 7 parameters. Conciseness is undermined by lack of essential information; it should include more context to be useful.

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?

The tool has 7 parameters, no annotations, no output schema, and many sibling tools. The description does not explain return values, pagination, or filtering capabilities. It is grossly incomplete for effective use.

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 43% (only 3 of 7 parameters have descriptions in the schema). The description adds no additional meaning to parameters. It fails to compensate for the low schema coverage, leaving agents uninformed about how to use parameters like top, page, or filter.

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?

Description states 'Lists BRC accounts.' which provides a verb and resource, but it is vague and does not distinguish from sibling list tools like brc_list_customers or brc_list_bank_accounts. It is unclear what 'BRC accounts' refers to.

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 on when to use this tool versus alternatives. Sibling tools include many other list operations, but the description offers no context about what type of accounts are listed or when to choose this over others.

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