get_silo_thermometry

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

With no annotations, the description carries the full burden. It discloses the 'latest snapshot' nature, includes specific data fields (fill percent, cable count, min/max/avg temperature in Celsius), and implies read-only behavior. This adds value beyond the bare schema, though it could mention error cases or data availability.

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 three concise, front-loaded sentences, each serving a purpose: what it does, what it includes, and when to use it. No redundant language.

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 the simplicity of the tool (one parameter, read-only), the description is sufficiently complete. It lists key output fields, and an output schema is present for detailed return values. It doesn't address edge cases, but these are less critical for a straightforward read operation.

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 0%, so the description must compensate. It clarifies that silo_id identifies the specific silo for the request, but adds no format or example. This is minimal but adequate for a single required string parameter.

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 clearly states 'Return the latest thermometry snapshot for one silo,' specifying the verb, resource, and scope. It distinguishes from siblings like list_silos or get_active_alerts by focusing on a single silo's thermometry data.

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 explicitly says 'Use this when the operator asks about a specific silo's health,' providing a clear when-to-use scenario. It doesn't mention exclusions or alternatives, but the context is sufficiently distinct from sibling tools.

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