Watch values for a bounded window

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

With no annotations, the description covers important behaviors: creates and cleans up internal subscription, bounded duration (300s), and return format. However, it does not mention whether the tool blocks, error handling, or polling behavior (though pollIntervalSeconds is in schema).

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?

Three sentences, each serving a distinct purpose: purpose, internal mechanism/cleanup, and return value. No unnecessary words, front-loaded with key information.

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 no output schema, the description explains the return format (per-element summary). However, it does not specify whether the tool is synchronous or asynchronous, if it blocks until duration completes, or what happens on errors or object deletion.

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 coverage is 100%, so the schema fully documents parameters. The description contextualizes parameters (e.g., 'bounded duration' for durationSeconds) but adds little beyond the schema, especially for pollIntervalSeconds which is not mentioned in the description.

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 the specific verb 'Monitor' with resource 'objects' and clearly states the bounded duration, internal subscription creation, cleanup, and return summary. It distinguishes from siblings like 'read_current_value' and 'get_history' by focusing on live changes over time.

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 explains what the tool does but does not explicitly state when to use it versus alternatives like 'read_current_value' or 'get_history'. There is no guidance on when-not-to-use or prerequisites.

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