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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description goes further by stating 'no side effects' and detailing that failed sections return {error, detail} instead of silently disappearing. This adds meaningful behavioral context beyond the annotations.

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 description is somewhat lengthy but well-structured, listing distinct output sections and next actions in a scannable format. Every sentence adds relevant detail, though some repetition (e.g., 'read-only, unmetered, no side effects') could be trimmed without loss.

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?

Despite lacking an output schema, the description thoroughly enumerates the returned sections (identity, deals, counts, next_actions, voice) and explains error behavior. This is sufficient for an agent to understand what the tool returns and how to interpret partial failures, making it complete in context.

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 has no parameters, and the description accurately reflects that by specifying no input expectations. The baseline of 4 for zero-parameter tools applies, and there is no missing parameter information to penalize.

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?

Clearly identifies itself as a session opener that returns identity, deal summaries, and recommended next actions, distinguishing it from the more focused connections_whoami and connections_execute siblings. The verb 'returns' and the explicit content list make its purpose unmistakable.

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?

Explicitly states it is the session opener and provides a ranked next_actions list with exact execute calls, guiding the agent to use it at the start of a session and follow up appropriately. Also notes it is read-only and unmetered, so the agent knows it can be safely called without side effects.

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