list_aws_organizations_settings

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

Beyond the readOnlyHint=true and destructiveHint=false annotations, the description elaborates on pagination behavior (pageToken usage), the fact that settings are customer-level and apply across all orgs, and that only activated product lines are returned. It also clarifies the meaning of purchaseAccountId. This adds substantial behavioral context not present in structured fields.

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 fairly long but well-structured, front-loading the core purpose and then adding context on scope, pagination, and product line activation. Each sentence contributes meaningful information, though it could be slightly trimmed without losing value.

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 complexity (settings retrieval with pagination, product line breakdown, customer-level config) and the absence of an output schema, the description covers all critical aspects: what is returned, scope, pagination behavior, purchaseAccountId meaning, and activation conditions. It is sufficiently complete for an agent to use 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?

Schema description coverage is only 25% (only customerContext has a description). The description adds clarity for pageToken in the pagination explanation but does not explain maxResults or X-Tenant-Id. It does not compensate fully for the missing schema coverage, leaving some parameter semantics to inference.

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: returning automation and recommendation engine settings for every onboarded AWS organization, broken down by product line. It distinguishes from siblings like list_aws_organizations (which lists orgs) and list_aws_recommendations (which lists recommendations) by explicitly mentioning 'settings' and the breakdown by product line.

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 explains when to use it (to get settings for commitments and organization-level configuration), that settings apply uniformly across organizations, and that only activated product lines are returned. It also provides pagination usage details. However, it does not explicitly name alternative tools for exclusion, though sibling names make the distinction implicit.

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