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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so safety is largely covered. The word 'Preview' adds real information about a staged/dry-run semantic, but the description never says whether a pending action is created, what must be done to commit it, or what permissions are required.

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?

A single ten-word sentence with no filler, so it is structurally tight. But its brevity comes at the cost of under-specification, and the few words it does spend describe target types the schema doesn't support.

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 4-required-parameter mutating tool with no output schema and zero schema coverage, the description omits the resource identity, role semantics, expiration, and the preview/confirm lifecycle. Almost everything an agent needs to call it correctly is missing.

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% for 5 parameters, so the description must compensate — and it does not. It never mentions resourceType, resourceId, role, or expiresAt, and its mention of 'organization' and 'public share' targets actively misleads, since only ACCOUNT/handle and TEAM/teamId are accepted.

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 verb+resource ('granting ... access') is identifiable, but the 'Preview' qualifier conflicts with the name and title ('Grant resource access'), leaving it unclear whether this applies or merely stages a grant. It also names target kinds ('organization', 'public share') that aren't in the schema's ACCOUNT/TEAM enum, so the stated scope doesn't match the tool's actual inputs.

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 guidance on when to use this versus the sibling resource_share_revoke, nor any mention of the likely confirm_action / cancel_action follow-up implied by 'Preview'. An agent must infer the whole workflow from the name alone.

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