get_org_service_events

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

No annotations are provided, so the description carries the full burden, and it does establish the core behavior: a read of health events scoped to one service and one organization. It is silent on practical traits such as time-range defaults, pagination, result limits, and permission requirements, which for a query tool with zero annotation coverage leaves real gaps.

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 one-line purpose statement is front-loaded and followed by tightly scoped parameter documentation and two short example prompts, each of which adds usable context. There is no filler, though the example prompts are a slight expansion beyond the minimum needed.

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 single required parameter is documented. What is missing is disambiguation from the dense cluster of sibling health/event tools and any indication of result scope (time window, pagination), which an agent would want before invoking.

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 0% — the single `service` property has no description at all — so the description must compensate, and it does: it names the AWS service, gives concrete examples ('EC2', 'RDS', 'LAMBDA'), and notes the value is case insensitive. That covers format, vocabulary, and a matching caveat the schema omits.

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 ('Get'), resource ('health events'), and scope ('for a specific AWS service across your organization'), which clearly separates it from the non-organizational get_service_events. The distinction is conveyed through the scope phrase rather than by naming the sibling tool, so an agent must infer the boundary rule.

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 intended usage ('What's happening with EC2 across my organization?'), giving a concrete sense of when to reach for this tool. However, there is no explicit guidance on when NOT to use it or how to choose among the many near-identical siblings like get_org_health_events, get_org_service_health, or get_service_events.

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