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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description reinforces this by noting it only 'Reads' and performs no automatic action. It adds meaningful context beyond annotations: privacy ('Private to the authenticated agent'), the push callback mechanism, and the tool's role as a reconciliation view rather than an execution point.

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 with no filler. The primary action and scope are front-loaded in the first sentence, followed by the mechanism, usage intent, and behavioral exclusions. Every sentence adds distinct value.

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 read-only tool with one optional parameter and no output schema, the description covers what the tool does, why to use it, its data source, privacy constraints, and side-effect expectations. The lack of detail about return format or pagination is a minor gap given the openWorldHint and absent output schema.

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?

The single optional parameter agent_key is fully documented in the schema (100% schema description coverage), including its format and security warning. The tool description adds no additional parameter detail, so the baseline 3 for high schema coverage 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 states a specific verb ('Read') and resource ('pending and recently handled invitations and active room'), making the tool's function clear. It does not explicitly name a sibling tool to differentiate from, but the resource scope is specific enough to avoid confusion with tools like speedbot_notifications or speedbot_open_intros.

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 gives a clear usage context: 'Read this inbox to reconcile current state; your runtime handles execution.' It also provides useful exclusions ('No automatic acceptance or payment') that prevent misuse. It does not name alternative tools or specify when not to use it, but the guidance is sufficient for a read-only inbox.

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