bunny_get_mc_app_overview

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read-only behavior is established. The description adds valuable context by specifying that metrics are 'real-time' and by enumerating what the returned overview includes, which goes beyond the structured annotations without contradicting them.

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 a single sentence that front-loads the core action and resource, then efficiently lists the key metrics. Every element earns its place, and there is no redundant or filler language.

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 single-parameter read-only retrieval tool with comprehensive annotations and schema coverage, the description is complete. It tells the agent exactly what the tool returns and includes the notable 'estimated cost breakdown' detail, which would not be obvious from the tool name or schema alone.

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 100%, and the sole parameter 'id' is already described as 'Application ID'. The description does not add extra meaning about the parameter beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

States the specific verb 'Retrieve' with the resource 'application overview' and enumerates the exact metrics returned: latency, CPU/RAM usage, active instance count across regions, and estimated cost breakdown. This clearly differentiates it from sibling tools like bunny_get_mc_app or bunny_list_mc_apps by focusing on overview metrics rather than app details or list operations.

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 does not mention when to use this tool versus alternatives such as bunny_get_mc_app or bunny_get_account. While the metric list implies a monitoring/overview use case, there is no explicit guidance on selecting this tool over others or any exclusion criteria.

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