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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false. The description adds useful context that this is an app-only adapter, returns connection/session metadata, does not create or accept invitations, and may select an already accepted shared route. However, it does not explain why destructiveHint=true is set or what destructive behavior is possible, which is a notable gap for a tool whose name/title suggest reading.

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-loads the tool's role as an app-only collaboration-panel adapter, then covers side effects, exclusions, and alternatives in a compact sequence. Every sentence adds useful routing or behavioral context without filler.

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 parameters and no output schema, the description gives enough context to call the tool: app-only scope, return category, exclusion of invitation creation/acceptance, and possible route selection. The main missing piece is clarification of the destructiveHint=true annotation, which leaves an important safety trait unexplained.

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?

The tool takes no parameters, so the baseline is 4. The description appropriately spends no time explaining parameter semantics.

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 resource and context: refreshes the workspace's shared-session status and incoming invitations for the collaboration panel. It distinguishes itself from get_connection and view_request_session, though the verb 'refreshes' leaves some ambiguity about whether it is purely a read or also a UI state update.

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?

Explicitly routes the agent to get_connection for model-driven account/session inspection and to view_request_session for requesting access via an invitation URL. It also clarifies that this tool does not create invitations or accept access, though it does not explicitly state the primary 'use when' condition beyond the collaboration panel context.

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