hcp_engagement_summary

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

With no annotations, the description carries the full burden. It discloses useful behavioral traits: sorted by most interactions first and including samples per HCP. However, it omits important context such as whether the operation is read-only, the time window for recency/interactions, and how sentiment score is defined or scaled.

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?

Two compact sentences with no filler. The first sentence front-loads the core output and sort order; the second provides a concrete use case. Every sentence earns its place.

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 description gives a reasonable outline of the result fields and ordering, but no output schema exists and annotations are absent so more weight falls on the description. It fails to clarify the meaning of 'samples', the recency window, sentiment scoring, or how the optional filters interact with each other and with the limit.

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 0%, and there are 4 parameters: tier, limit, region, and specialty. The description only indirectly references tier via the 'Tier A HCPs' example and says nothing about limit, region, specialty, their defaults, or filter behavior, so the agent must infer most parameter meaning from names and enum values alone.

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?

Description clearly identifies the resource (HCP engagement analytics) and specific metrics: total interactions, recency, sentiment score, and samples per HCP. Although it lacks an explicit action verb like 'returns' or 'computes', the metric list and sorting behavior sufficiently distinguish it from sibling tools such as hcp_list_interactions and hcp_visit_frequency_by_segment.

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 states a clear use case: finding engagement gaps, with a concrete example (Tier A HCPs with no recent contact). It does not explicitly mention when not to use it or name alternatives, but the use case provides enough context for an agent to select it appropriately.

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