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

Annotations declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, covering the safety profile. The description adds no behavioral context beyond 'no participant bodies', whose meaning is unclear, so the agent still doesn't know what calling this does or returns.

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?

It's short, but the phrase 'six fire choices' and 'independent current admission observations' are front-loaded yet unintelligible. Brevity here reflects under-specification rather than efficiency.

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 no-parameter entry-point tool with no output schema, the description must explain what happens on invocation. Instead it's opaque, leaving an agent unable to predict the result or follow up 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, so the baseline is 4; the description has nothing to explain and doesn't mislead about inputs.

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 reads as cryptic, undefined jargon: 'six fire choices', 'independent current admission observations', 'no participant bodies'. It doesn't state a verb or resource an agent could recognize. Nothing distinguishes it from siblings like yac_list_fires or yac_read_fire.

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?

'Start here' is a faint hint that this is an entry point, but it doesn't explain when to call this instead of the sibling tools. No prerequisites or exclusions are given.

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