reports_slow_rendering_rate_get

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

No annotations are present, and the description does not disclose behavioral traits like authentication requirements, rate limits, side effects, or whether the operation is read-only. The description adds no insight beyond the schema.

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 at one sentence, which is front-loaded, but it sacrifices necessary detail. It is minimally adequate but lacks structure to convey key information efficiently.

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 complexity (one required param, no output schema, no annotations) and the presence of numerous sibling report tools, the description is incomplete. It fails to differentiate itself or explain the parameter sufficiently.

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 0% description coverage, and the description adds no meaning to the sole parameter 'name'. It does not explain what 'name' refers to (e.g., app package name, report ID), leaving the agent uncertain.

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 'Get' and the resource 'slow-rendering-rate metadata', distinguishing it from related tools like reports_slow_rendering_rate_query. However, 'metadata' is vague and does not specify what aspects are included.

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 such as reports_slow_rendering_rate_query or other report tools. There is no context about prerequisites or scenarios.

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