list_my_contacts

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

Description states it lists active contacts and returns details, implying read-only. But without annotations, it fails to mention authentication, rate limits, or sorting behavior. Adequate but not exhaustive.

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?

Description is short and front-loaded with the main purpose. The Args and Returns sections are clear but slightly redundant given the output schema. Still concise overall.

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 simple paginated list, the description covers input and output basics. Missing default pagination behavior, sorting order, and handling of empty results. Adequate but incomplete.

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 0% (no parameter descriptions in schema). The description adds 'page number for pagination' and 'number of items per page', but doesn't explain defaults (null) or behavior when omitted. Minimal added value.

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 clearly states the tool lists the user's contacts, specifying it returns active contacts with details like handle, email, and type. This clearly distinguishes it from sibling tools like 'list_agent_contacts' or 'remove_my_contact'.

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 on when to use this tool versus alternatives like 'list_my_peers' or 'list_my_agents'. No not-use conditions or prerequisites are mentioned.

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