get_contact_list

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

Given no annotations, the description declares 'Read-only', which discloses non-destructive behavior. It does not address authentication, rate limits, or other traits, but the key behavioral trait is covered.

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 sentence with no redundant words. Every part earns its place: it specifies nature (read-only), action (retrieve), resource (contact list), and identifier (by ID).

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 retrieval tool with one parameter and no output schema, the description is adequate. It could hint at what details are returned, but the core purpose is fully communicated.

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 schema covers the single parameter with a description. The tool description adds no extra meaning beyond the schema, so 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 clearly states the tool retrieves one contact list by ID, using the verb 'retrieve' and specifying the resource. It is distinct from siblings like 'list_contact_lists' (lists all) and 'update_contact_list' (mutates).

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 'Read-only' label indicates when to use (for retrieval without modification) but does not explicitly exclude other use cases or mention alternatives. However, the context is clear for a simple get operation.

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