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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context by listing what the response contains (contact details, company, owner, tags, custom fields) and noting the underlying endpoint, though it says nothing about auth, errors, or whether a missing id returns 404 vs null.

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?

Extremely tight: one front-loaded clause naming the resource and scope, followed by the returned fields and the REST endpoint. No filler sentences and no repetition of the title.

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-entity getter with one required parameter, full schema coverage, and annotations that already carry the safety profile, the description is nearly sufficient. It even compensates for the absent output schema by summarizing response contents, though it omits any error/not-found behavior.

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 single person_id parameter is fully described in the schema (100% coverage), including type, positivity constraint, and meaning. The description's 'by id' adds no format or syntax detail 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 resource and scope: a single person (lead or contact) retrieved by id, with an explicit enumeration of the returned data. This clearly distinguishes it from the plural sibling pipelinecrm_list_people and from the other get_* tools that target companies, deals, notes, etc.

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?

Usage is only implied by 'by id' – an agent can infer this is the right tool when it already holds a person id and should use pipelinecrm_list_people otherwise. No explicit when-to-use, prerequisites, or named alternatives are given.

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