get_bedrock_hourly_usage_stats

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

No annotations exist, so the description carries full burden. It only states it returns a formatted string, with no mention of side effects, permissions, rate limits, or other behavioral traits. The 'detailed breakdowns' is vague.

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 single sentence plus structured Args/Returns. No redundant information. The format is clear and front-loaded.

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?

For a tool with one parameter object (three sub-properties) and no output schema, the description provides minimal context. It specifies the return type as a string but not the content format. The 'detailed breakdowns' hint is insufficient for an agent to fully understand the output.

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 description coverage is 0% for the top-level 'params' property, so description must compensate. It mentions 'number of days to look back and region', which partially maps to the sub-properties, but omits 'log_group_name'. The summary adds some context but incomplete.

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 it retrieves hourly usage statistics with detailed breakdowns, matching the tool name. It distinguishes from 'get_bedrock_daily_usage_stats' via the 'hourly' qualifier, but does not differentiate from 'get_detailed_breakdown_by_day' or other siblings.

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 provided on when to use this tool versus alternatives like 'get_bedrock_daily_usage_stats' or 'get_detailed_breakdown_by_day'. No usage conditions or exclusions are mentioned.

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