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

Annotations already declare this as readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds only that the returned content is an 'exact agreement' plus an invitation — useful framing, but no detail on permissions, whether the agreement is project-scoped, or what happens if no invitation exists.

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?

A single short sentence with the temporal qualifier front-loaded at the end; nothing is wasted. It is efficient, though the brevity borders on under-specification rather than true 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?

For a simple read-only tool whose annotations carry the safety profile and with no output schema to explain, the description is minimally sufficient: it says what is read and when. It still leaves the required project_id unexplained and gives no sense of failure modes or return shape.

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% and the description mentions neither parameter. The possessive 'your' loosely implies agent_key is implicit, but project_id — the required parameter — is completely undocumented in both schema and description, so the agent gets no help on what identifier to supply.

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 read operation over an 'invitation and exact agreement', which is a clear verb+resource pairing. However, it never names the project/product context that distinguishes it from siblings like speedbot_product_project or speedbot_product_accept, and 'Read your invitation' is broad enough that an agent must infer the tool's actual scope.

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 trailing clause 'before accepting' implies the sequencing relative to speedbot_product_accept, which is genuinely useful routing. But it stops short of an explicit when-to-use statement, does not name the alternative tool, and gives no guidance on prerequisites or what to do with the agreement once read.

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