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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the interaction model (the client shows a Connect button), the session effect (once signed in, every call is that account's), and the guest fallback. It stops short of covering repeat invocation, already-signed-in state, or failure modes.

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?

What the tool does is front-loaded in the opening clause, and the benefit, mechanism, session effect, and guest fallback follow in short sentences. Slight wordiness in the closing guest-mode sentence, but nothing is redundant.

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 zero parameters, an output schema, and annotations covering the safety profile, the description carries only the behavioral burden and mostly meets it. The main gap is what a caller should do if the person is already connected or declines.

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 applies; there is nothing for the description to disambiguate. It correctly implies the only input is a user action in the client rather than arguments.

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 names a concrete verb and resource: it signs the person in to their ReflowPDF account, and it is distinct from every document-handling sibling. It does not explicitly say how it differs from those siblings, but the account/session framing makes its role unambiguous.

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 exactly when to use it: when the person wants unmarked PDFs, their plan's page allowance, or documents persisted in their account. It also names the alternative and its cost - everything works as a guest, but with a small mark - so the agent can weigh use vs. skip.

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