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

Annotations only give destructiveHint=false and idempotentHint=false; the description earns credit by explicitly stating no messages are sent outside, nothing is deleted, and every change is reversible via the opposite action. That clarifies the mutation's blast radius beyond the annotations, though it omits per-action differences (e.g. assign side effects).

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 sentence is well front-loaded and carries the key facts, but the appended '— FR :' translation is a pure duplicate that adds no information and dilutes the definition.

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 4-parameter mutation with no output schema, the description covers scope and reversibility but leaves parameter behavior and per-action requirements undocumented; an agent still cannot confidently call assign vs read from the description alone.

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 only 25% (only assign_to is described). The description names the actions but says nothing about message_ids batching (max 100), workspace_uuid scoping, or that assign_to requires an assign action — so it does little to compensate for the coverage gap.

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 (organize) plus resource (inbox conversations) and enumerates the exact action set (read/unread, archive/unarchive, assign), which maps directly to the action enum. It is clearly separable from siblings like reply_to_inbox_message and list_inbox.

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 action list implies when the tool is appropriate, but there is no explicit when-to-use vs alternatives guidance (e.g. use refresh_inbox to fetch, reply_to_inbox_message to respond) and no stated prerequisites or exclusions.

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