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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: only 'active' accounts are returned, empty results mean Nife-hosted, and no credentials are exposed — the last being a meaningful negative disclosure an agent would otherwise not know.

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?

Four short sentences, front-loaded with the core action and followed by the downstream use and the empty-list edge case. The deploy_site digression slightly dilutes focus but each sentence carries distinct information.

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 single-parameter read tool with an output schema already present, the description covers what is needed: scope, filtering to active accounts, empty-list semantics, and the credential exclusion. The return payload shape itself is correctly left to the output schema.

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 100% and organization_id is already documented as coming from list_organizations, so the schema does the heavy lifting. The description adds downstream meaning to the returned account id (used as cloud_account_id in deploy_site), but says nothing about the input parameter beyond what the schema provides.

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 with scope: 'List the organization's active AWS cloud accounts.' The 'active' qualifier plus the organization scoping makes it distinguishable from siblings like list_organizations and list_sites without opening either schema.

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?

It gives clear context for why an agent would call this: to obtain a cloud_account_id to pass into deploy_site rather than using Nife's own AWS account. It does not name any exclusions or alternative tools for listing accounts, but the usage path is unambiguous.

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