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

Annotations already cover read-only safety (readOnlyHint=true, destructiveHint=false), but the description adds critical context: the data is from third parties and should be read but not acted upon. This is a key behavioral nuance not captured in annotations. It doesn't describe pagination or rate limits, but the safety guidance is valuable.

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 English portion is concise and front-loaded with purpose, then usage, then safety. However, including a full French translation roughly doubles the length without adding value for most agents, slightly hurting conciseness.

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 should ideally explain the return shape (e.g., list of conversations with metadata), but it doesn't. It does cover key context: what it lists, from where, and the refresh limitation. Overall fairly complete but missing return format details.

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 67%, which is moderate. The description adds no further parameter semantics beyond what's in the schema; it doesn't explain the filters (type, status, provider) or the limit default. Baseline of 3 is appropriate since the schema provides some descriptions and the description doesn't compensate for the gaps.

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 (List) and resource (inbox conversations), names the three content types (comments, private messages, mentions), and specifies the sort order (most recent first). This clearly distinguishes it from sibling tools like get_inbox_thread, refresh_inbox, and manage_inbox_messages.

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?

Explicitly states to use refresh_inbox to fetch newer ones, which is a critical distinction because list_inbox only returns already-collected conversations. This prevents the agent from incorrectly assuming it fetches fresh data.

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