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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It indicates a read operation ('List') but does not mention any filters behavior, pagination, defaults, or potential side effects. It also does not address what happens when no filters are provided or the meaning of the filter parameters.

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 appropriately short and front-loaded, containing only four words. However, it is under-specified due to its brevity, lacking necessary details about filters and behavior. It is not verbose, but it is too sparse to be considered well-structured for a tool with multiple parameters.

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 has three optional parameters and no output schema or annotations, the description is far from complete. It does not cover the meaning of the filters, any constraints, or expected return values. The description provides only the minimal function, leaving the agent without essential context to use the tool 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?

With 0% schema description coverage, the description must explain all parameters, but it only says 'with filters' without defining no_mfa, system, or account_type. The generic mention of filters provides minimal semantic value, but it does not explain what each parameter does or expected input formats.

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 function: listing accounts with filtering capability. It uses a specific verb ('List') and resource ('accounts'), which is unambiguous. However, it does not differentiate from sibling tools like access_review, though the name and description are fairly distinct.

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?

The description gives no guidance on when to use this tool versus the siblings. It provides no context, no prerequisites, and no alternatives. The usage is only implied by the straightforward name, but explicit guidance is missing.

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