Get incoming lead

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

The description simply restates the name and parameter without adding behavioral context. Annotations already declare readOnlyHint=true and openWorldHint=true, so the description provides no additional transparency about return format, errors, or lead properties.

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 a single sentence, concise and front-loaded. It communicates the essential action and parameter without any unnecessary words.

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 get-by-id tool, the description covers the core purpose. However, there is no output schema to describe the return value, and the description does not mention what an incoming lead is or what data will be returned, leaving some context incomplete.

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 schema has 0% description coverage for the 'uid' parameter. The description clarifies that uid is the unique identifier used to fetch the lead, which adds meaning beyond the bare type string. However, it doesn't provide format or validation details.

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 action (get) and the resource (incoming lead) with the specific lookup key (UID). It distinguishes this from list/summary tools by indicating a single entity retrieval.

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 implies usage when you have a UID and need a single incoming lead, but it doesn't explicitly state when to avoid using this tool (e.g., when listing or when using regular leads). No alternatives are mentioned.

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