reports_excessive_wakeup_rate_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'query', which implies a read operation but does not confirm idempotency, safety, or whether any side effects occur. No details on permissions, rate limits, or what the response contains are given.

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 in length but sacrifices necessary detail. It is not front-loaded with critical information beyond the basic action. While brevity can be positive, here it results in 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's complexity (8 parameters, nested objects, no output schema, no annotations), the description is far from complete. It fails to explain the query structure, return format, pagination, filtering, or any context required to use the tool effectively.

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 schema has 8 parameters with 0% documentation coverage per the context signals. The description adds no meaning to any parameter; it only mentions 'timeline' which corresponds to timelineSpec, but fails to explain how to use dimensions, metrics, filter, userCohort, pageSize, pageToken, or name.

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 verb 'query' and the specific resource 'excessive-wake-up-rate timeline', making the purpose identifiable. However, it does not differentiate from sibling query tools like reports_crash_rate_query or reports_excessive_wakeup_rate_get, so it lacks full sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives such as the get endpoint or other query tools. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction.

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