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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read only' in the description is largely redundant. What the description does add is the content of the response (sending mailbox identity and reconnect state), which is genuine value given there is no output schema.

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?

A single short sentence with the substantive information front-loaded. The trailing 'Read only' earns little since annotations already carry that, but the text is far from bloated.

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 must carry the return-value burden, and it does state the two things returned: the sending mailbox and its connection state. Scoping details (per-user vs account-wide, what a disconnected state looks like) are missing but not blocking for a zero-argument read.

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 zero parameters, so there are no parameter semantics to document and the baseline applies. The description correctly does not invent or imply any inputs.

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 the specific resource (the mailbox emails are sent from) and the specific state it reports (whether reconnection is needed), which is a concrete read operation rather than a restatement of the name. It is reasonably distinguishable from the connect-link sibling, though it never explicitly frames itself as a status check for that flow.

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?

There is no explicit when-to-use guidance and no named alternative, even though soclo_leads_mailbox_connect_link is the obvious follow-up when reconnection is needed. The phrase 'whether it needs reconnecting' faintly implies a diagnostic-then-connect flow, but the agent must infer it.

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