leadbrew_get_lead

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the input requirement but does not disclose whether the operation is read-only, if authentication is needed, or any rate limits. As a retrieval tool, it should explicitly state it does not modify data.

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?

The description is two sentences long with no extraneous information. It front-loads the purpose and immediately provides the necessary usage condition. Every word adds value.

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 tool with one parameter and no output schema, the description adequately explains what the tool returns (detailed info including email and phone) and the required input (lead ID). No additional context is needed given the low complexity.

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?

The input schema fully describes the 'id' parameter (100% coverage). The description adds minor context by reaffirming the ID comes from a previous search and implicitly allowing a LinkedIn handle, but this does not significantly enhance understanding beyond the schema.

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 clearly states the verb 'Get' and the resource 'specific lead', and specifies the contents of the returned information (email addresses and phone numbers). It distinguishes itself from sibling tools like leadbrew_get_company and leadbrew_search_leads by targeting a single lead by ID.

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 advises that the lead ID must come from a previous search, providing clear usage context. However, it does not explicitly state when not to use this tool or mention alternatives such as leadbrew_search_leads for broader queries.

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