pipedrive_get_lead

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

The description adds no behavioral context beyond the annotations, which already declare the tool safe (readOnlyHint, destructiveHint false, idempotentHint). It does not disclose any additional traits like rate limits, authentication needs, or what 'detailed information' encompasses. With annotations carrying the burden, the description is adequate but not enriching.

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, clear sentence with no unnecessary words. It conveys the purpose efficiently and is front-loaded.

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?

The tool has a single parameter, annotations provide safety guarantees, but there is no output schema. The description says 'detailed information' without specifying return fields, which is vague. For a retrieval tool, more detail on what exactly is returned would improve completeness, but the current description is minimally acceptable.

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% for the single parameter `id` (described as 'Lead UUID'). The description adds no new meaning beyond confirming the schema, so it meets the baseline of 3.

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 tool's action ('Get detailed information'), the resource ('a specific lead'), and the identifier method ('by UUID'). It distinguishes itself from sibling tools like `pipedrive_list_leads` and `pipedrive_search_leads` which operate on collections or searches.

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 specific lead UUID and need details. However, it does not explicitly state when to use this tool versus alternatives like `pipedrive_list_leads` or `pipedrive_search_leads`, or mention any prerequisites or context. The guidance is minimal.

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