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

With no annotations provided, the description must disclose behavior on its own. It reveals that the tool 'returns the exact policy with confidence tier and any unresolved operations,' which is useful output context. However, it doesn't explicitly state whether this is a read-only operation or if it makes any AWS changes, leaving ambiguity about side effects. This is a clear gap.

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 composed of two sentences that are direct and informative. The first sentence states the purpose, the second explains inputs and outputs. Every word contributes value, with no fluff or repetition of schema details. This is exemplary conciseness.

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 there is no output schema, the description does a good job of outlining the return content: 'exact policy with confidence tier and any unresolved operations.' It could be more detailed about the exact structure or error cases, but for a relatively simple generation tool, it covers the essential information needed by an agent.

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 input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds meaningful semantics by indicating the parameters are alternative input modes ('Pass a named workflow, explicit IAM actions, or a description'), which clarifies that you should provide at least one but not all. This goes beyond the schema's individual descriptions.

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 the tool's function: 'Generate a least-privilege IAM policy for an AWS workflow.' It uses a specific verb (generate), specifies the object (IAM policy), and is distinct from sibling tools like list_workflows and query, which perform different functions. This makes the purpose unambiguous.

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 explains that you can provide 'a named workflow, explicit IAM actions, or a description,' which gives clear input options. However, it doesn't explicitly state when to use this tool over alternatives or mention using list_workflows to discover workflow names, so there's room for improvement but the usage context is clear.

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