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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context: pending/unavailable means no valid summary, counts cover full adjacent windows, only the leading 30 groups are returned, and the caller must not infer complete source coverage or a live feed. No contradiction with annotations.

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?

Four dense, non-redundant sentences with the purpose front-loaded and every caveat earning its place. There is no filler or repetition of schema fields.

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?

Behavioral caveats and count/truncation semantics are well covered, and there is no output schema to fill in return-shape details. However, the unexplained expected_input_stamp parameter and the unstated output shape leave an incomplete picture for an agent.

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 does not explain either parameter. view_id is somewhat inferable as the Live view identifier from the tool name and schema, but expected_input_stamp's purpose is completely opaque. The description fails to compensate for the missing schema documentation.

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 opening sentence names the exact operation ('Read') and resource ('current guarded summary for a configured Live view'). The caveats about pending/unavailable and truncated group counts further disambiguate it from sibling list/search tools.

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?

Clear context is provided: this reads the current guarded summary for a configured Live view, with explicit behavioral expectations such as no retained pagination and not inferring complete coverage. It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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