Get Service Limits

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

With no annotations provided, the description must carry the behavioral burden, but it only states a read-style action ('Get'). It does not disclose whether it is safe, whether it requires credentials, how it handles regional differences, or whether quotas come from the current account or environment.

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 front-loaded sentence with no filler. It loses a point because it is so terse that it provides almost no operational value beyond the tool name.

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?

Although an output schema is present, the description still leaves essential context missing: how to specify the service, what the returned limits represent, and what prerequisites exist. For a tool with no annotations and no parameter documentation, this is insufficient.

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 coverage is 0% and the description adds no meaningful meaning to the 'service' parameter beyond the schema's type string. It does not provide examples, expected format, or clarify what counts as an AWS service identifier, so an agent is left guessing how to populate it.

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 clear verb and resource: getting service quotas and limits for an AWS service. It is distinct enough from sibling tools like get_account_info or get_context, though it does not explicitly differentiate itself from potential similar quota tools.

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?

No guidance is given about when to use this tool versus alternatives such as aws_query, get_best_practices, or get_rightsizing_recommendations. It does not mention required setup, like an active profile or selected account, or exclusions.

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