list_environment_blueprints

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

No annotations are provided, so the description carries the burden. It describes the function and return values but does not disclose behavioral traits such as whether the operation is read-only, any side effects, rate limits, or authentication requirements. The mention of pagination via next_token is useful but incomplete.

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 a clear one-liner, followed by Args and Returns sections. It is concise, though slightly verbose with parameter patterns. Every sentence adds value, making it easy to parse.

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?

With an output schema present (though not shown), the description already explains return values. It covers all parameters, pagination, and filtering. However, it lacks context on when to use this list vs. other related tools, which is addressed in the usage guidelines dimension.

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 adds significant meaning beyond the input schema. It explains each parameter's purpose, constraints (e.g., patterns, min/max length, default values), and filtering behavior. This compensates for the 0% schema coverage, providing rich semantics.

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 states 'Lists environment blueprints in an Amazon DataZone domain.' It uses a specific verb ('Lists') and resource ('environment blueprints') and distinguishes from sibling tools like get_environment_blueprint (singular) and list_environment_blueprint_configurations.

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 explicit guidance on when to use this tool versus alternatives. The description lists parameters but does not indicate the expected context or exclusions. The purpose is clear, but usage context is implied rather than stated.

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