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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral detail beyond that: visibility is role-dependent and invitations expire after 7 days. It does not describe response shape, but the added access-scoping and expiry context is valuable.

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 compact and front-loads the key id=space fact, with no filler or repetition. It could be slightly improved by starting with a clear verb phrase like 'List space invitations,' but overall it is efficiently written.

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?

With five parameters and no output schema, the description partially covers what the agent needs: it explains scope and expiration. However, it does not clarify the shape of the returned invitation/request objects, what 'requests' versus 'invitations' means in the output, or default ordering, so an agent may still be uncertain about the response.

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 input schema already documents all five parameters at 100% coverage, including limit, cursor, detail, and max_tokens. The description adds the important semantic that 'id' is a space identifier, which is not clear from the generic schema description of id as a resource ID.

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 makes clear the tool concerns reading requests/invitations in a space, with editors seeing all requests and other agents only their own invitation. It does not include an explicit 'list' verb or name sibling tools for differentiation, but the intent is unambiguous from the name and context.

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 useful access-related context: editors can read all requests/invitations, other agents only their own, and invitations expire after 7 days. However, it does not state explicit when-to-use guidance or contrast with siblings like list_space_members or list_space_proposals, so usage is mainly implied.

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