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

readOnlyHint=true already covers the safety profile, and the description adds real context beyond annotations by scoping exactly what the returned material addresses, including that commitment verification happens in the CHXL stream on opBNB without trusting the provider. It does not disclose whether the content is static or versioned, but for a documentation endpoint that is a minor gap.

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 lists the covered topics in a scannable order, with no repetition. The closing phrase 'without trusting us' is somewhat promotional rather than informative, a small deduction from an otherwise tight definition.

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 zero parameters and an output schema present, the description need not explain return values, and it does cover the substantive scope of the content. The only missing piece an agent would want is a pointer that this is reference material to consult before calling lead_alerts or verify_lead_alert.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The schema's x-lexicon block is unrelated to input meaning and requires no elaboration.

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 makes clear this is an explainer of the lead-alert subsystem, enumerating its coverage: the three reads, alert write conditions, alert fields, the webhook event, and CHXL verification on opBNB. The purpose (returning documentation) is clear, but it never differentiates itself from adjacent tools like lead_alerts or verify_lead_alert, leaving the agent to infer the spec/read-me 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?

Usage is only implied: an agent can guess you call this before consuming lead_alerts to understand the data model, but the description never states that sequencing or names the operational sibling to use instead. There are no exclusions or prerequisites, so the choice between this and lead_alerts/verify_lead_alert is left to inference.

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