Workspace Grant Workspace Access

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety/mutation profile is covered. The description adds no behavioral context beyond that — nothing about idempotency, permission requirements, or what happens on a conflicting grant.

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 tight lines, front-loaded verb+resource with parameter values following. No filler, though the terse style leaves obvious gaps rather than being complete and compact.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. Still, for a 4-required-param mutation tool with 0% schema coverage, the definition omits two parameters and any prerequisite/permission context, leaving it only minimally viable.

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%, so the description carries the burden. It usefully documents grant_type ('member'/'team') and permission ('view', 'explore', 'organize'/Contribute, 'edit'/Manage), which are not in the schema as enums. However, workspace_id and grantee_id are entirely undocumented — notably the expected grantee_id format (member vs team id) is left ambiguous.

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+resource ("Grant workspace access"), which is enough to distinguish it from the sibling list/delete grant tools (workspace_list_workspace_grants, workspace_delete_workspace_grant). It does not explicitly name or differentiate against those siblings, so it stops short of a 5.

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?

There is no when-to-use guidance, no prerequisites (e.g. admin/caller permission level needed to grant), and no mention of the alternative grant tools. The agent must infer the context entirely from the name.

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