get_aws_organization

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds that it returns a single organization and includes specific stats, but it does not disclose potential caveats like data freshness, pagination, or rate limits. With annotations covering the safety aspects, the description adds some value but not extensive behavioral detail. No contradiction with annotations.

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 concise, uses a bulleted list to enumerate the returned stats, and front-loads the purpose. It is structured clearly, though it could be slightly tighter by avoiding the opening tagline. Overall, it is readable and efficient.

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 3 parameters, an output with nested stats (no output schema), and no output schema. The description lists the main return components but does not detail the structure of each stat like monthlyStats or dailyCoverage. Given the complexity of the response, the description is somewhat incomplete for an agent to understand the full data shape, but the overall purpose is clear.

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 low (33% - only customerContext has a description). The description does not explain the parameters like managementAccountId or X-Tenant-Id, relying on the schema's basic types and pattern. The description mentions the output stats but not how parameters affect the response. Since coverage is low, the description should compensate more; it does not.

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 returns a single AWS Organization with metadata and specific stats. It distinguishes from siblings by focusing on a single organization retrieval versus list operations like list_aws_organizations or account-level tools. The verb 'get' is clear, and the resource is 'AWS Organization' with commitment context.

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 what the tool returns and mentions it drives the customer Overview screen, implying use for fetching organization-level commitment data. However, it does not explicitly state when to use this tool versus alternatives like get_aws_account or list_aws_organizations, nor does it provide exclusions or conditions. The context is clear but not explicit about alternatives.

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