list_measurement_windows

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

Annotations declare readOnlyHint=true, covering the safety profile. The description adds ordering behavior ('newest first') and a definitional clarification ('tracking snapshots'), but does not disclose other behavioral details like pagination or default limits. With annotations present, this is acceptable baseline.

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, correctly front-loaded sentence that conveys the core purpose and key ordering detail with zero wasted words.

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 simple list tool with readOnlyHint and two optional parameters, the description is minimally adequate. However, it does not explain what data is returned (no output schema) or the semantics of 'status' and 'limit', leaving notable gaps for an agent to make informed invocations.

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%, and the description provides no information about the 'limit' or 'status' parameters. The agent must infer their meaning from names alone, with no guidance on allowed values or how they affect results. The description does not compensate for the lack of schema descriptions.

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 a specific verb 'List' and identifies the exact resource 'measurement windows' with a clarifying parenthetical 'tracking snapshots' and ordering 'newest first'. This clearly distinguishes it from sibling tools that list prompts, citations, recommendations, etc.

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 implies this is the tool for listing measurement windows, which provides clear context for when to use it. However, it does not explicitly mention alternatives or when not to use it, but the resource name is distinct enough among siblings.

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