capture_observations_now

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

The description openly labels the operation as 'Mutating', explains that it persists observations and refreshes cached metrics, and discloses return values. This adds meaningful behavioral context beyond the idempotentHint annotation, which alone would not reveal the persistence side effect.

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 compact and well-structured: a one-line summary, a clear side-effect warning, and a usage directive. Every sentence earns its place, and the most important 'Mutating operation' label is front-loaded.

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 action with no output schema, the description fully covers what the tool does, its side effects, what it returns, and when to use it. Nothing essential is missing for an agent to invoke it correctly.

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?

There are zero parameters and schema coverage is 100%, so there is no parameter burden for the description to carry. The description adds relevant conceptual context like 'bounded batch', but no parameter-specific semantics are needed.

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 ('Capture') with a clear resource ('aggregate UniFi health observations') and a temporal qualifier ('immediately'). It clearly distinguishes this tool from passive query tools like query_observation_trends.

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?

Explicitly states when to use this tool: 'Use before query_observation_trends to ensure recent data, or rely on scheduled capture otherwise.' This provides both a selection condition and a named alternative, making it easy 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.