anon_post_invites

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false). The description adds genuinely new context: the member:manage authorization requirement, the one-time nature of the open link, and that the project is derived from the API key rather than a parameter. It stops short of explaining reversibility or the returned resource.

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?

Purpose is front-loaded, followed by precondition, behavioral branch, sharing mechanic, and route. No redundant sentences; the frontend concatenation note earns its place as an operational detail.

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 mutation tool with no output schema, the description covers the essentials: permission gate, the two invite modes, and implicit project scoping. It leaves the return payload (presumably the url) and the roleName field unaddressed, which are the main remaining gaps.

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?

Reported schema coverage is 0%, so the burden falls on the description, which it partially meets: it explains targetUserId's two very different meanings (open link vs. restricted invitee) far beyond the terse schema note. However it says nothing about roleName or expiresInHours, leaving part of the nested body unexplained.

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 and resource (create project invite) and immediately branches into the two distinct modes of the operation. An agent can tell exactly what this tool does and how it differs from read-oriented siblings.

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?

It gives clear conditions for choosing between the open-link path (omit targetUserId) and the targeted path (pass targetUserId), plus the required member:manage permission. It does not name or contrast with any sibling tool, so it stops short of the 5-level when-not/alternative guidance.

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