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

Annotations already declare readOnlyHint/non-destructive/openWorld=false, so the safety profile is covered. The description usefully adds that external grants (outside Higgs Hub) are included and that returned permissionId values are what you pass to a revoke call. It doesn't mention pagination or result ordering, but adds real context beyond the annotations.

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 front-loaded sentence where each clause earns its place: the core action, the external-grant scope, and the permissionId payoff. No filler or redundancy, though it is dense enough that it reads as one packed clause chain.

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 two-parameter read-only tool with no output schema, the description covers purpose plus the key output payoff (permissionId) and the non-obvious inclusion of external grants. The notable gap is any explanation of the itemId parameter, but overall it is adequate for correct invocation.

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 coverage is only 50%: the mailbox parameter is documented (with a pointer to list_authorized_mailboxes) but itemId has no description at all. The description only vaguely implies 'a file' and says nothing that disambiguates the itemId identifier or its expected format, so it fails to compensate for the undocumented parameter.

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 and resource ('List everyone with access to a file') and adds scope ('including grants made outside Higgs Hub'), which clearly separates it from sibling mutations like unshare_gdrive_item or share_gdrive_item. It does not name a sibling for contrast, 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?

Usage is implied: you call this to audit access before revoking, hinted by 'with the permissionId needed to revoke one'. There is no explicit when-to-use/when-not or direction to the parallel list_onedrive_permissions, so the guidance remains inferential.

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