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

Annotations already establish the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description still adds real value: the owner/admin authorization requirement, the fact that no email is dispatched, and that historical as well as current invitations are returned. It does not disclose pagination behavior or result-size limits, which for a list tool is the remaining gap.

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?

Two tightly written sentences with zero filler; the resource and scope lead, and the disambiguating side-effect disclaimer follows. Every clause carries information.

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 read-only, two-parameter listing tool with full annotation coverage, the description covers purpose, permission requirement, side-effect absence, and the returned fields, which partly compensates for the missing output schema. The only material omission is any hint about paging through a potentially large invitation history.

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 says nothing about the two parameters, so limit/offset and their pagination semantics are left entirely to the agent to infer from bounds and defaults. The one thing that would help a listing tool, how results are paged or capped, is absent.

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 and resource ('List ... workspace invitations') plus scope ('current and historical') and enumerates the fields returned (recipient, role, revision, delivery/acceptance state). The closing clause 'Reading never sends email or accepts membership' implicitly separates it from the sibling send/revoke/prepare invitation tools, so an agent can place it without opening the schema.

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?

Gives an explicit access prerequisite ('Owner/admin only') and an implicit when-to-use boundary by clarifying this is a read that does not send email or accept membership, which routes the agent away from helvabase_send_workspace_invitation. It stops short of naming those alternative tools or stating when to prefer them over this listing.

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