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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by disclosing the breadth of returned details (deal totals, e-commerce order summaries, owner, tasks) and the underlying endpoint, though it does not mention not-found behavior or error handling.

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 front-loaded sentence that starts with the core purpose before listing details. The field enumeration is long but informative and directly relevant to what the tool returns.

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 tool with no output schema, the description is fairly complete: it names the resource, states the key lookup, and enumerates the major return categories. Minor gaps remain around exact response structure and error cases, but the essential context is present.

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 coverage is 100%, and the single contact_id parameter is fully documented in the schema with its source (revampcrm_list_contacts). The description adds no further parameter detail, so the baseline of 3 is appropriate.

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 states a specific verb/resource: 'One contact by id with full details.' It clearly distinguishes this from sibling list/search tools by emphasizing retrieval of a single contact by id and enumerating the detailed fields returned.

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 implied by 'by id' and the schema note that the id comes from revampcrm_list_contacts, so an agent can infer this is for fetching one known contact. However, the description does not explicitly state when to use this instead of list_contacts or other contact-related tools.

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