agent_status_refresh

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description is consistent with those (a refresh that persists state), but adds little beyond clarifying that it both refreshes and returns a snapshot. It does not explain what gets rewritten or what 'RSS' refers to.

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?

A single front-loaded sentence that states the action followed by the return behavior. Zero filler, though the brevity leaves the ambiguous 'RSS' term unglossed.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile. Still missing is any indication of how this differs from the very similar agent_status/tasks_refresh siblings or what the refresh actually mutates.

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 single parameter json_output has 0% schema description coverage, and the description says nothing about it or about how output format is controlled. With low coverage the description was expected to compensate, and it does not.

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?

States a specific verb ('Refresh') and a concrete resource ('persisted task RSS/lifecycle state') plus the side effect of returning a snapshot. However, it does not distinguish itself from close siblings like agent_status or tasks_refresh, and 'RSS' is left undefined for an agent to guess at.

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?

There is no statement of when to call this rather than agent_status, tasks_refresh, or live_status. The agent gets no trigger condition, no preconditions, and no exclusions.

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