List Contacts In Folder

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the basic operation but adds no details about behavior such as whether it returns only direct folder members, if pagination is needed, or if any side effects occur. The description is minimal and largely redundant with the tool name.

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 brief and to the point. The additional Chinese intent phrases add some bulk but are not excessive, and the main sentence is efficient. It is not overly verbose, meriting a score above the minimum.

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 list operation, the description covers the core purpose, and the schema fully documents parameters. However, it lacks any usage guidance or behavioral context beyond what the tool name implies, so it is only minimally complete for effective tool selection.

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%, with both 'top' and 'folderId' documented in the input schema. The description does not add additional meaning to these parameters beyond the schema, so the baseline score of 3 is appropriate.

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 action: 'List personal contacts in a selected contact folder.' This specifies the verb (list), the resource (personal contacts), and the scope (in a selected folder), distinguishing it from sibling tools like contacts_list (lists all contacts) and contacts_list_folders (lists folders).

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 alternatives. It does not mention contacts_list, contacts_search, or contacts_list_folders, nor does it give any context about prerequisites or exclusions. The Chinese intents merely offer synonyms for the same action, providing no usage differentiation.

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