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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so the safety profile is covered. The description adds useful behavioral context on the empty-return case (disabled/stale/unavailable plus the no-action instruction), but the cryptic 'wake' terminology and lack of return-format detail limit the added value.

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 tight sentences with the primary action front-loaded and the empty-case caveat following. Every clause carries weight, though 'acknowledge its wake' is less economical in clarity than in length.

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?

No output schema exists, so the description carries the return-value burden, and it only addresses the empty case. For a private, credential-gated read tool, the positive (non-empty) return shape and the meaning of 'wake' are left unexplained, leaving a moderate gap.

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 both connection and suggestion_id are already documented, and connection carries the private-credential guidance itself. The description adds no syntax or format detail for suggestion_id, matching the baseline 3 when the schema does the work.

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 ('refresh') and resource ('one private suggestion'), which distinguishes it from the plural suggestions_list and the mutating suggestion_resolve. The 'before acting' framing adds intent, though 'refresh' is slightly ambiguous about whether it retrieves or re-evaluates.

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?

'before acting' implies the pre-action context and the empty-case handling ('acknowledge its wake without action') gives some operational guidance. However, no sibling alternatives (suggestions_list, suggestion_resolve) are named and the condition for choosing this over them is left to inference.

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