mailkite_get_list

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

The annotations already include readOnlyHint=true, and the description adds the meaningful behavioral context that a management session token is required. It also states the return includes the member count. No contradiction exists; the added auth and return context go beyond the annotation.

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, focused sentence with no filler. It front-loads the core action and scopes the result, then gives the prerequisite. Every word adds value.

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 tool with one simple parameter, a read-only annotation, and no output schema, the description covers the core elements: what it retrieves, the distinguishing output (member count), and the required token. Nothing essential is missing for an agent to correctly invoke this simple GET-style tool.

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 already describes the only parameter `id` as a path parameter, with 100% schema description coverage. The description does not add any semantic detail about the id itself, only that it refers to a contact list. The baseline of 3 is appropriate because the schema handles the parameter documentation.

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 ('Get'), a specific resource ('one contact list'), and a distinctive output ('member count'). It is clearly differentiated from sibling tools like mailkite_list_lists by the singular 'one' and by not being a list-all operation.

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 clearly conveys that this tool is for retrieving a single contact list, which implies it should be chosen when a specific list is needed rather than when listing or mutating lists. It also names a prerequisite (management session token). However, it does not explicitly name alternatives or give when-not-to-use guidance.

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