list_active_contacts

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

With no annotations, the description carries full burden but merely says 'List all active contacts.' It does not disclose whether the operation is read-only, destructive, or requires authentication, nor does it mention pagination, rate limits, or return format.

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?

At three words, the description is overly terse. While concise, it omits essential information about parameters, behavior, and usage context, sacrificing clarity for brevity.

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?

Despite having an output schema and numerous siblings, the description fails to explain parameter 'top', return values, or how this tool differs from similar listing tools. It is incomplete for effective agent 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?

The single parameter 'top' (integer, default 0) has no schema description and is not explained in the tool description. Schema coverage is 0%, and the description adds no meaning about its purpose (e.g., pagination limit).

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 'List all active contacts' uses a specific verb and resource, clearly distinguishing from sibling tools like 'list_contacts' (which likely includes inactive contacts) and 'list_contacts_for_date_range' (date-filtered). It precisely states the tool's scope.

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?

No guidance is provided on when to use this tool versus the many sibling tools for listing contacts (e.g., list_contacts, list_contacts_for_date_range). There is no mention of prerequisites, alternatives, or exclusions.

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