reports_lmk_rate_query

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

No annotations are provided, so the description bears full responsibility for behavioral traits. It only says 'Query LMK-rate timeline' with no mention of read-only nature, side effects, rate limits, pagination, or output format. This is insufficient for an 8-parameter tool.

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 front-loaded with the verb 'Query'. It is concise but perhaps too sparse; it earns its place but could include additional clarifying context without losing conciseness.

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 of 8 parameters (including nested timelineSpec), no output schema, and no annotations, the description is severely incomplete. It fails to explain what the tool returns, how pagination works, or how to construct queries. It is not complete enough for an agent to use 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?

Schema description coverage is 0%, meaning no per-parameter descriptions. The description does not compensate by explaining the 8 parameters (dimensions, metrics, timelineSpec, filter, etc.). The schema's top-level description 'Standard MetricSet query body' is vague. The tool description adds no parameter context, leaving the agent uninformed.

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 'Query LMK-rate timeline' clearly states the verb (query) and resource (LMK-rate timeline), distinguishing it from sibling reports_lmk_rate_get which likely returns a single snapshot, not a timeline. However, it does not explain what 'LMK' stands for, but in context it's presumably low-memory killer.

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 vs alternatives. Sibling tools include reports_lmk_rate_get and other rate query tools (e.g., reports_anr_rate_query, reports_crash_rate_query), but the description does not compare or specify context such as 'use for time-series data' or 'use when timeline details needed'.

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