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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partially covered. What the description does not disclose is meaningful: whether reconnect triggers a new OAuth/IMAP authorization handshake, whether it requires a prior get_sender_connect_link step, whether existing credentials are invalidated, or whether it is rate-limited by the provider. For a state-changing sender operation, those are exactly the facts an agent needs.

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?

The text is short with no filler, but that brevity comes from under-specification rather than tight editing, and the name is redundantly repeated before the dash. There is no structure beyond a single clause.

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?

An output schema and annotations exist, so return values and safety are partly covered. However, the description leaves the core mechanic of "reconnect" unexplained — whether it is an automatic retry, a re-authorization flow, or a token refresh — which is the single most important thing for an agent deciding to call it.

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 description coverage is 100% and both parameters (id, workspace_id) are documented in the schema, including the default-workspace fallback behavior. The description adds nothing on top of that, so the baseline of 3 applies.

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 is a near-verbatim restatement of the tool name and title: "Reconnect Sender - Reconnect a failed sender". The only added information is the precondition that the sender is in a failed state. Nothing distinguishes it from related siblings such as get_sender_connect_link, get_sender_health, or update_sender.

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 guidance on when to use this versus get_sender_connect_link (which appears to be the link-generation counterpart) or update_sender. The word "failed" hints at a precondition but no exclusions, prerequisites, or alternative paths are given.

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