List Radar leads

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

With no annotations, the description carries the full burden and does disclose two behaviors: default sort order (newest first) and that verdicts appear only once qualified. It omits pagination, result limits, and any auth/permission context.

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 short sentences, front-loaded with what is returned and the scoping rule. Efficient overall, though the phrasing 'Leads Radar saved earlier' is slightly telegraphic.

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-param list tool with no output schema and no annotations, the description covers ordering and content but says nothing about pagination, volume, or access requirements. Adequate minimum, not complete.

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% (baseline 3), and the description adds real meaning beyond the schema's bare provenance note: passing chatId restricts the listing to a single search. That semantic of the parameter is not in the schema itself.

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 resource (Radar leads saved earlier) and its ordering ('newest first') plus returned content ('their verdict once qualified'). Distinguishable from find_leads and qualify_radar_leads, though it never names a sibling to explicitly separate itself.

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?

'Pass a chatId for one search only' implies when the optional parameter narrows scope, but there is no explicit statement of when to use this tool versus find_leads or qualify_radar_leads. Usage is inferable rather than stated.

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