List Communication Threads

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it returns a paginated JSON array with metadata and mentions the endpoint. It does not disclose additional traits like rate limits or authentication needs, but annotations cover safety sufficiently.

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 four sentences and front-loaded with purpose. Each sentence serves a function: stating purpose, giving use case, describing return format, specifying parameters, and API context. No redundant or extraneous information.

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?

Given no output schema, the description explains the return format (paginated JSON array with metadata) and required parameters. It also provides the API endpoint and tool area. However, it could elaborate on filtering capabilities or thread semantics for completeness.

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?

With 100% schema coverage, the description adds minimal value beyond the schema by reiterating page/per_page for pagination and highlighting required params. It does not explain parameter formats or constraints beyond what's in the schema, so baseline 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 tool returns a list of email communication threads and enumerates Emails for paginated overview, finding IDs, or filtering. However, it does not explicitly differentiate from numerous sibling list tools like 'list_of_emails' or 'list_communication_tags', missing the chance to distinguish its specific 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?

The description advises using this tool for paginated overviews, finding IDs, or filtering, and mentions required parameters and pagination controls. However, it provides no guidance on when not to use it or outlines alternatives among sibling tools, leaving the agent to infer suitability.

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