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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive/closed-world behavior, so the safety profile is covered. The description adds only that the lead is selected via lead_id or lead_uuid; it says nothing about pagination behavior, ordering, or empty-result handling that annotations don't cover.

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 tight sentence with the resource front-loaded and the identifier clarification in parentheses. No waste, though it could have spent one more clause on required-identifier behavior.

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 no output schema and 0% schema coverage on four parameters, the description should explain the returned submission shape, pagination, and identifier requirements. It conveys only the object of the listing, leaving significant gaps for a paginated listing tool.

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 description coverage is 0% across 4 parameters, so the description is the only source of semantics. It explains lead_id/lead_uuid as alternative identifiers but does not resolve whether at least one is required, what happens when both or neither are supplied, or what page/per_page control.

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 ('List') and resource ('a lead's submissions'), and clarifies that the target lead is identified by lead_id or lead_uuid. It is clearly distinct from delete_lead_submit and set_lead_submit_stage, though it doesn't explicitly name siblings like list_leads.

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?

No guidance on when to use this versus list_leads or other lead-related tools, and no mention of prerequisites or which identifier to prefer when both are available. The agent must infer usage entirely.

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