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

No annotations are provided, so the description carries the full burden, and it does supply the key safety trait 'Read-only'. However, it discloses nothing beyond that — no behavior on missing/invalid IDs, no auth or scope requirements, and no note on whether the record must exist — leaving most behavioral questions open for an unannotated tool.

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 that front-loads the payload ('Full lead card:') followed by a compact field list and a trailing 'Read-only.' No wasted text, though the parenthetical quip about source is slightly loose.

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 single-record get with no output schema, the field enumeration usefully substitutes for a return-value spec, which is a real contribution. But with no annotations and no output schema, the missing id semantics and error behavior leave the definition adequate rather than 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 description coverage is 0% and the sole parameter (id) is never mentioned, so the description adds no meaning beyond the schema. The agent must infer that 'id' is the lead identifier from the 'Full lead card' phrasing alone.

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 states a clear resource ('Full lead card') and enumerates the returned content (identity, source, company enrichment, activities, comments, assignments), so the agent knows this fetches rich detail for a single lead. It does not explicitly differentiate from the sibling crm_list_leads, relying on the title's 'one' to convey the single-record scope.

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 when-to-use guidance, no prerequisites, and no named alternative such as crm_list_leads or crm_get_conversation. Usage is only weakly inferable from the field enumeration.

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