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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful context about the output composition (synthesis and contributing anomaly IDs) and the semantic nature of convergence events, but it does not disclose ordering, pagination, or any look-back limits beyond the schema's default.

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 one concise sentence with no filler. The core resource and key output attributes are front-loaded, making it easy for an agent to scan.

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 simple read-only query with one optional parameter and no output schema, the description adequately explains the domain concept and return payload. It omits explicit return-type/list semantics and potential caveats, but the annotations and schema cover the most important operational details.

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% for the single 'hours' parameter, which already documents type and default. The description only loosely ties 'recent' to the time window and adds no additional format, range, or edge-case detail, so it does not need to compensate.

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 identifies a distinct resource ('convergence_events') and explains it as 'anomaly-of-anomalies', which helps differentiate it from sibling query tools. It also states what the result includes: synthesis and contributing anomaly IDs. It lacks an explicit verb such as 'list' or 'returns', but the tool name and 'Recent...' phrasing make the operation clear.

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 guidance on when to use this tool versus alternatives like query_thermal_anomalies, query_precursor_matches, or query_regime_shifts. The unique resource name is the only implicit signal, and no exclusions or alternative routing are provided.

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