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

No annotations are provided, so the description carries the full burden. It discloses the default scoping behavior (all chatbots when botId is omitted) and what data the leads contain, but says nothing about result volume, pagination, or any limits — meaningful gaps for a read tool with zero annotation coverage.

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?

Two well-formed sentences with the core purpose front-loaded and no filler. The second sentence largely duplicates the schema's botId description, so it earns its place only marginally.

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 one-parameter read tool with no output schema, the description adequately sketches the returned data (visitor message, contact details, lead types). It does not cover pagination or result-size expectations, which an agent might still need.

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% and the single optional parameter is already fully documented in the schema. The description restates the same omit-for-all behavior rather than adding format or semantics beyond it, so the baseline 3 applies.

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?

States a specific verb (Retrieve) plus resource (leads) and even enumerates the lead subtypes it returns — contact requests, appointment bookings, callback requests. It is clearly distinct from the update_lead sibling, but it never names or contrasts with any sibling tool, which the 5-level requires.

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 botId scoping rule ('Without botId, returns the leads of every chatbot in the account') implies when to pass a filter, but there is no guidance on when to reach for this tool versus get_fit/get_quote/update_lead or any stated prerequisites. Usage is inferable rather than explicit.

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