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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing beyond that — no mention of not-found behavior, whether the lead is fetched live from the external Lawcus instance, or permission scoping.

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?

Four words are certainly front-loaded and waste nothing, but the terseness crosses into under-specification rather than efficiency; a single clause on return content or failure mode would cost little and add much.

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 single-record fetch with no output schema, the description gives no indication of what a lead record contains or how the caller should handle a miss. Annotations cover the read-only safety question, but the retrieval contract itself is left entirely implicit.

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 0%, so the description must carry the load; "by UUID" does identify the single parameter's meaning and confirms it is a lead identifier. However it adds no detail beyond the regex already visible in the schema — no note on where a lead_uuid is obtained.

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?

"One lead by UUID" implies a single-record retrieval and distinguishes it from the sibling lawcus_list_leads by singularity, but it never uses an explicit verb (get/fetch/retrieve), so the operation type must be inferred from the tool name rather than the description.

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 statement of when to use this versus lawcus_list_leads or lawcus_search, no prerequisites, and no note about what happens when the UUID is unknown. The agent must infer routing from the tool name alone.

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