get_pricing_service_attributes

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

Annotations declare readOnlyHint=true, and the description adds context about default region behavior (AWS_REGION env var), case-insensitive regex filtering, and return value format (list of attribute names). This goes beyond the annotation without contradicting it, though it doesn't discuss edge cases like empty results or error handling.

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 well-structured with clear headers (PURPOSE, WORKFLOW, PARAMETERS, RETURNS, NEXT STEPS, EXAMPLE). Every section adds value, and the purpose is front-loaded in the first sentence. No filler or redundancy.

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?

Given the tool's moderate complexity, the description covers purpose, parameters, return values, usage order relative to sibling tools, and an example. Even with an output schema present, it explains what the return data looks like ('List of attribute names'), making it self-contained.

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 100%, so baseline is 3. The description adds examples for service_code ('AmazonEC2', 'AmazonRDS'), explains the region parameter's default and why it matters, and illustrates the filter regex with examples. This enriches the schema descriptions meaningfully.

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 opens with a specific verb+resource: 'Get filterable attributes available for an AWS service in the Pricing API.' It clearly distinguishes itself from siblings by focusing on filterable attributes, and the workflow section explicitly contrasts with get_pricing_service_codes and get_pricing_attribute_values.

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 explicit workflow guidance: 'Use this after get_pricing_service_codes()' and instructs to use get_pricing_attribute_values() next. It also tells users to match the region to get_pricing(), giving clear when-to-use and alternative paths.

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