Set a member's project access

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

Goes well beyond the destructiveHint annotation by disclosing that changes take effect on the member's next request, propagate to their API keys and MCP connections, that an owner is exempt, and that out-of-selection projects appear nonexistent.

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?

Single dense paragraph that front-loads the access semantics before prerequisites; every sentence carries information, though the run-on structure could be broken up for faster scanning.

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 destructive, permission-gated mutation with no output schema, it covers effect timing, blast radius, exemptions, parameter sourcing, and the confirmation protocol — everything needed to invoke it safely.

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?

With only 33% schema coverage, the description compensates well: it explains memberId provenance (from list_members, not the user id), projectIds provenance (list_projects), mode semantics, and the confirmationToken flow. organizationId is the one parameter left 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?

States a specific verb+resource ('Set which projects of the organization a member reaches') and immediately defines both modes, making it clearly distinct from siblings like change_member_role and invite_member.

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?

Explicitly routes the agent: tells it to call preview_operation with tool "set_member_project_access" first, show the plan, and only proceed after user agreement, plus required permission and role.

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