snapshot

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

No annotations provided, so the description carries the full burden. It doesn't state whether the call is read-only, whether it has side effects, whether it's rate-limited, or what 'combined' means. Only 'Return' implies a read, which is minimal.

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 with no filler. Efficient, though perhaps too terse given the tool's surface area.

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?

Output schema exists, so return values don't need explaining. But with no annotations and zero parameter documentation, the definition is missing too much: no indication of scope ('bridge telemetry' undefined), no parameter meaning, no safety profile. Inadequate for an agent deciding whether to call it.

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 mentions no parameters at all. Three boolean parameters (include_state, include_mission, include_inventory) exist but are undocumented in both places. The description doesn't compensate for the coverage gap, but baseline for low coverage with a reasonable parameter count is around 3.

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+resource: 'Return a combined snapshot of bridge telemetry'. Clear what it does, though 'bridge telemetry' is somewhat vague and it doesn't distinguish itself from siblings like poll_events, get_system_health_alerts, or version.

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?

No guidance on when to use this vs alternatives, no prerequisites, no mention of what 'bridge telemetry' comprises or when a snapshot is preferable to event polling or polling state separately.

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