inspect_target_health

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

No annotations are provided, and the description does not disclose whether the operation is read-only, requires specific AWS permissions, or what output is returned (though an output schema exists). The term 'Inspect' implies a safe read, but this is not explicitly stated, and side effects or rate limits are not addressed.

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 a single, empty-free sentence that directly states the tool's purpose. It could be more informative, but it is appropriately brief for the simple tool.

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 is simple with two required parameters and an output schema, but the description lacks usage context and behavioral disclosure. Given no annotations and minimal description, it does not fully prepare an agent for when and how to invoke it, though the output schema covers return values.

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 description does not explain the parameters 'target_group_arn' and 'region'. With 0% schema description coverage, the description needed to compensate, but it only mentions the resource generally. The parameter names are self-explanatory, but no added context (e.g., ARN format or region default) is given.

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 identifies the action ('Inspect') and resource ('target health for one target group'). It distinguishes from sibling tools which focus on ECS services, events, task definitions, and logs, not target health.

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 provides no guidance on when to use this tool versus the sibling inspection tools. It doesn't specify prerequisites (e.g., need a target group ARN) or typical scenarios (e.g., troubleshooting unhealthy instances). No alternatives or exclusions are mentioned.

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