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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds 'subscription status' as a useful output detail, but it does not disclose behaviors like error handling, required permissions, or data freshness. This is adequate but not rich.

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: 'Get the full profile of a specific contact including subscription status.' Every word earns its place, and there is no redundant or filler content.

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 is a simple read-only getter with one well-documented parameter, behavioral annotations, and an output schema. The description is sufficient for basic invocation, though it could be slightly more complete by pointing to how to obtain a contactId. Overall, no critical missing information for correct use.

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%: each parameter already has a description, and the sole parameter contactId is documented as 'The contact ID.' The description's 'specific contact' reinforces the parameter's role but adds no meaningful semantic detail beyond the schema, so the baseline of 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?

The description uses a specific verb and resource: 'Get the full profile of a specific contact.' It also adds a distinguishing detail, 'including subscription status,' which clarifies the scope of the returned data and separates it from more narrow sibling tools like get_contact_nudge_context.

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 gives no explicit guidance on when to use this tool versus siblings such as droptrack_search_contacts or droptrack_get_label_contact_360. It does not mention prerequisites, exclusions, or alternatives, so an agent must infer usage from the name and parameter alone.

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