get_org_service_health

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

With no annotations, the description carries the full disclosure burden. It does add useful behavioral context — the results are 'current' and limited to 'active' events spanning all accounts — but it says nothing about the elevated permissions org-wide access typically requires, nor about pagination or result limits for large organizations.

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 purpose is front-loaded in the first sentence and the example prompts are a compact, scannable aid. Mild redundancy between 'current AWS service health events across your organization' and 'active health events across all accounts in your AWS Organization' costs it a point.

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?

An output schema exists, so return values need not be explained, and the parameterless signature keeps the surface small. What is missing is the piece an agent actually needs: how this differs from the closely named org-level siblings and what access level is required.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool is 4. No parameter meaning is lost.

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 states a specific verb and resource (get AWS service health events) with an explicit organizational scope (all accounts in the AWS Organization). However, it fails to differentiate itself from near-identical siblings such as get_org_service_events, get_org_health_events, and get_org_account_events, leaving an agent unable to tell which org-level health tool to pick.

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 two example prompts imply the usage context (org-wide service disruptions affecting multiple accounts), which is better than nothing. But there is no when-not guidance and no explicit mention of alternatives like get_service_health (single account) or get_org_scheduled_changes, so the routing decision is left to inference.

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