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 adds genuine behavioral context by saying the output is scoped to this connection's permissions and separates areas where permissions are missing from actions that only exist in the app. It stops short of describing the response shape or granularity.

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: the first defines the output, the second defines when to invoke it. Front-loaded with the payload description and no filler or repetition of the title.

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 and no parameters, the description carries the burden of explaining what comes back, and it does so at a conceptual level (capabilities by area, missing permissions, app-only actions). It lacks detail on format and on whether permission gaps are account-level or connection-level, but an agent has enough to call it correctly.

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?

There are zero parameters, so the schema imposes no documentation burden and the baseline is 4. However, the description adds nothing about how the summary is scoped or filtered (e.g., all areas at once versus a caller-selected area), so it does not fully exploit the freedom a parameterless tool provides.

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 description gives a concrete verb ("Resume" / summarize) and a concrete resource (what this connection can do in PilotControl, broken down by area, plus missing permissions and app-only actions). This is unmistakably a capability-discovery tool and cannot be confused with any of the ~70 action-oriented siblings.

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 states the trigger condition explicitly: use it when the user asks for something and you don't know whether a tool exists. It also names the failure mode it prevents (telling the user something can't be done), which is a strong, actionable routing rule.

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