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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful non-obvious context beyond that: that an observed sighting is weak evidence and does not establish a grounded answer. It does not discuss pagination or freshness beyond the timestamp field, but the semantic caveat is the higher-value addition.

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 dense sentence with the primary object front-loaded and the caveat trailing. "Grounded answer" is somewhat jargon-dependent, slightly reducing immediate clarity, but there is no filler.

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?

With an output schema present and fully documented parameters, the description need only convey scope and interpretation, which it does. The remaining gap is routing guidance relative to the other widget_* tools.

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% with both parameters fully described, including provenance hints (agents_list/agent_create, channels_list). The description adds nothing about parameters, which is acceptable at full coverage but earns only the baseline.

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 names a specific verb ("Reads") and the exact resource contents (install code, last observed site origin/time), which is more precise than the title alone. It stops short of naming how it differs from siblings like widget_settings_read or widget_enable, so an agent must infer the boundary.

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?

There is no statement of when to call this versus widget_settings_read, widget_enable, or widget_settings_edit. The caveat about sighting not proving a grounded answer hints at interpretation of results rather than call selection, leaving usage entirely implicit.

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