get_kendra_costs

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

The description discloses key behaviors: listing indexes, showing edition and cost metrics, and flagging oversized/unused indexes. The 'account' parameter is noted as reserved for future use, adding transparency. No annotations are provided, so the description carries the full burden.

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 concise, with a clear paragraph followed by an Args section. Every sentence provides useful information without 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?

The description covers the main outputs (editions, costs, query volume, flags) adequately. With an output schema present, the description focuses on the tool's function. It could mention pagination or sorting, but is generally complete for a list tool.

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 single parameter 'account' is described in the Args section as 'Reserved for future multi-account support.' This adds meaning beyond the schema's type/default, explaining its purpose and current non-functionality.

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 that this tool analyzes Amazon Kendra costs by index, listing specific attributes (edition, cost, query volume, cost per query) and flags. It distinguishes itself from sibling cost tools like get_bedrock_costs by focusing on Kendra.

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 implies the tool is for Kendra cost analysis but does not explicitly state when to use it versus alternatives or provide any exclusions. However, the context of sibling tools makes the purpose clear.

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