reports_excessive_wakeup_rate_get

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

No annotations are provided, so the description bears full responsibility. It gives no behavioral details such as whether this returns a single record or list, any required permissions, or side effects. The extreme brevity offers no transparency.

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, which is concise but excessively terse. It lacks structure such as bullet points or separation of intent from behavior. Key information is missing, so conciseness becomes under-specification.

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 the tool has one required parameter, no output schema, and several sibling tools with similar names, the description is insufficient. It does not explain what 'metadata' includes, how 'name' is used, or how this differs from similar 'get' and 'query' tools.

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 'name' has 0% schema description coverage, and the description adds no explanation of what 'name' refers to (e.g., app name, metric name?). This leaves the agent without necessary context to correctly populate the parameter.

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 uses 'Get' + 'excessive-wake-up-rate metadata', clearly stating the action and resource. However, it does not differentiate from the sibling tool 'reports_excessive_wakeup_rate_query', which likely performs a similar query function. The term 'metadata' is vague.

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 provided on when to use this tool versus alternatives like reports_excessive_wakeup_rate_query. The description is entirely silent on usage context, preconditions, or exclusions.

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