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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: results are ordered newest first, and dead links are returned without a shareUrl, which an agent would otherwise misread as missing data. No pagination or permission notes, but the key behavioral quirk is disclosed.

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 sentences, both front-loaded: the first leads with scope and ordering then enumerates returned fields, the second leads with the use cases. The parenthetical about dead links is the only aside and it carries necessary meaning.

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 no output schema, the description is the sole source of return-shape information and it covers label, liveness, shareUrl, expiry and usage counts. Usage and the downstream revoke linkage are covered too; only edge details like pagination or an empty-list result are unaddressed.

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 100% and both parameters (flowId, workspace) are documented in the schema, including the token/workspace-key nuance. The description adds nothing about parameter semantics, so the baseline 3 applies.

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 ('Every guest link on one flow') and immediately scopes it to a single flow, distinguishing it from the workspace-level or flow-level siblings. It also names workbench_flows_shares_revoke, so an agent can place it relative to the share lifecycle without opening a 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?

Gives three concrete use cases ('who has access', recovering a lost link, obtaining the shareId for revoke), which is clear when-to-use guidance. It stops short of stating exclusions or explicitly contrasting with workbench_flows_share_create, so it is strong but not exhaustive.

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