list_org_accounts

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

Discloses that it syncs metadata to local DB for future queries and is free. No annotations provided, so description carries full burden; it does so adequately with no contradictions.

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?

Three concise sentences covering purpose, requirement, and examples. No extraneous content, well-organized.

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 parameterless tool, the description covers purpose, behavior (DB sync), prerequisites, and cost implications. Complete for an agent to invoke correctly.

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?

No parameters exist, so schema coverage is 100%. The description adds no param details, but the baseline for 0 parameters is 4.

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?

Clearly specifies action (list) and resource (AWS Organization member accounts), with distinctive details like sync to local DB and permission requirement. Distinguishes from sibling tools like `list_accounts` and `list_aws_accounts` by targeting org accounts.

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?

States required permissions and mentions free vs Team plan for cost rollup. Lacks explicit when-not-to-use or alternatives, but the context is clear enough for selection.

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