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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds non-obvious behavior: results are restricted to what the caller can read, out-of-scope queries return not-found, and for 'loads' only folders you can read are named — real behavioral 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?

Front-loading is good — the first sentence is a usable summary — but the action inventory is a single semicolon-chained wall of text that would be far easier to parse as a list. Density is high with little waste, yet the structure works against scanning and the run-on form hurts usability.

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?

With an output schema present, return shapes need not be described, and the description still covers all 13 actions, their arguments, defaults, and the not-found scoping rule. It is complete for the common cases; pagination/volume behavior and per-action output hints are the only omissions.

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 100%, so the baseline is 3, but the description adds cross-field semantics the schema does not: target 'defaults to you' and must be 'yours or one below you' for loads, scope_type defaults to folder or is inferred from a pasted console link, and location/node carry accepted link forms. These conditional constraints genuinely extend the schema.

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 opening sentence names the resource and its three question families (who can read what, pending decisions, identity/tree), then enumerates all 13 actions with the specific object each returns. An agent can tell this is the read-only access dispatcher versus the mutating siblings access_grant/access_revoke without consulting either schema.

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 a clear scope rule — 'Answers only about what you can read yourself; anything else answers not-found' — and every action line names the arguments it needs, which effectively routes the agent to the right action. It never explicitly contrasts when to pick this tool over access_grant/access_revoke, so it stops short of full when/when-not guidance.

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