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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the field inventory of the response, which is genuinely useful given there is no output schema, but it omits auth requirements, rate limits, and the Elite-plan caveat on customer_journey mentioned in the schema.

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 sentences, front-loaded with the core purpose, with the endpoint tacked on as a compact identifier. The long field enumeration is dense but each item is informative for a schema-less response, so nearly every word earns its place.

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 read whose annotations carry the safety profile and whose 100%-covered schema documents both params, the description closes the main gap by enumerating returned fields in the absence of an output schema. Missing only error/not-found behavior and the plan-tier caveat needed to call it fully correctly.

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 100%, so both parameters (lead_id, customer_journey) are already documented with format and provenance. The description adds only the field-list framing and no per-parameter syntax or behavior beyond the schema, 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 (get) and resource (a single lead by id) and explicitly enumerates the breadth of returned fields, which cleanly separates it from whatconverts_list_leads. An agent can pick this over the list sibling without opening either schema.

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 description never says when to use this tool versus whatconverts_list_leads or whatconverts_update_lead, and offers no prerequisites or exclusions. The only routing hint (lead_id sourced from whatconverts_list_leads) lives in the schema, not the description.

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