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

Annotations already declare read-only, non-destructive, closed-world behavior, so the description's added context is meaningful: results are scoped to the caller's own invitations, private message bodies are excluded, and joining requires an explicit accept action. It does not cover pagination behavior, but it adds genuine privacy and workflow context beyond the annotations.

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?

Three short sentences with little waste and the scoping rule front-loaded. The opening fragment is slightly cryptic, but overall it is efficient rather than bloated.

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 simple two-parameter read tool with annotations covering safety and no output schema, the description gives enough context to understand scope and privacy. It omits how cursor/limit drive pagination and does not point to the tool used to accept an invitation, leaving gaps in the retrieval workflow.

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 0%, so the description needs to explain limit and cursor, but it mentions neither. An agent can infer standard names and defaults from the schema, but the description adds no semantic meaning for either parameter.

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 the resource and scope ('Own invitations only') but uses a sentence fragment without an explicit verb, relying on the title 'Read your invitations' for the action. It does not differentiate this read tool from siblings such as collaboration_messages or collaboration_threads.

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 phrase 'Accept explicitly before joining' hints at a related workflow but names no alternative tool or condition for choosing this listing over siblings. There is no when-to-use or 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.