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 no behavioral detail beyond what the annotations and schema already provide, such as pagination behavior or result set expectations.

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 entire description is one compact sentence that leads with the verb and resource. Every word contributes to defining the operation with no filler.

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 simple, has 100% schema coverage, a read-only annotation, and an output schema, so the one-sentence description is largely sufficient. It loses a point for not providing any pointer to alternatives, leaving the agent to infer when search_contacts is the right choice among several contact-related siblings.

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%, so limit, cursor, and search are already documented in the schema. The description's mention of name, email, or company adds no new meaning because the search parameter's schema description already states it. 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?

The description states a specific verb ('search'), resource ('contacts'), and the filter fields ('name, email, or company'), making the operation clear. It does not explicitly name sibling tools like droptrack_get_contact_details or droptrack_list_label_contacts, so differentiation is implicit rather than explicit.

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 this tool is for finding contacts by search terms, but it provides no explicit when-to-use guidance or exclusions relative to sibling tools. There is no mention of when to prefer droptrack_get_contact_details for a single contact or droptrack_list_label_contacts for label-scoped listing.

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