poll-tasks

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

With no annotations, the description must carry behavioral context. 'Poll' and 'refresh' imply a non-mutating read of current task data, and 'app-only' is a useful access constraint. However, it does not disclose output format, polling mechanics, potential side effects, or whether it returns a snapshot vs. a change set, leaving some ambiguity.

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 with no wasted words. The main action is front-loaded, and the parenthetical adds the necessary contextual constraints without bloat.

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 zero-parameter app-only polling endpoint, this is largely complete: it states what data is returned, who should use it, and why. It does not explicitly describe the response shape or any refresh semantics, but the low complexity and absent output schema make that a minor gap rather than a blocking one.

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 input schema is empty with 100% coverage and zero parameters, so the description has no parameter behavior to document. Per baseline for zero-parameter tools, a 4 is appropriate; no parameter information is missing.

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 ('Poll') and resource ('current task data'), and clarifies that it is app-only and exists for visualization UI refresh. This distinguishes it from the sibling tools in purpose, though it does not explicitly name them or contrast directly.

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 phrase 'app-only, used by the visualization UI for refresh' gives a clear usage context and implicitly excludes general-purpose task querying or one-off viewing. It stops short of explicitly naming when-not-to-use alternatives, but the context is strong enough for an agent to route correctly.

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