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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: that teammate chats are excluded from results and that a Cotlet API key with app access is required.

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?

Front-loaded with the core purpose and reasonably tight. Slight redundancy in the title-style lead-in ("Your Inbox conversations with clients: who, unread flag and last message") being restated in the next sentence, but nothing extraneous beyond that.

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?

With no output schema, the description carries return-value burden and does so adequately (who, unread flag, last message), plus scope, exclusions and auth needs. Pagination is left to the cursor parameter in the schema, which is acceptable for this complexity level.

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 100%, so limit, cursor and unread_only are already documented in the schema. The description restates the unread flag semantics ("get what needs an answer") but adds no syntax or range detail beyond what the schema supplies. 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?

States a specific verb+resource ("Lists your Inbox conversations with clients") and enumerates what each row contains (who, unread flag, last message). It also scopes out team chats explicitly, so an agent can tell it apart from get_conversation and message tools.

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?

Guidance is implied rather than explicit: "Set unread_only to get what needs an answer" hints at a triage use case, but there is no statement of when to pick this list over everfit_get_conversation or everfit_send_message. The alternative named (Team tab) is a product surface, not a tool.

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