get_connection_status

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

Description discloses masked headers, ping query behavior, and latency measurement. Annotations already indicate safe and idempotent, but description adds valuable specifics.

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 efficient sentences front-loading the main purpose and then optional usage. Every word adds value.

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?

Given no output schema, description sufficiently covers what the tool returns (endpoint, masked headers, auth state, schema cache state, and optional ping results). Complete for a status tool.

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?

Single parameter ping is clearly described in both schema and description. Description adds context about the {__typename} query and latency measurement beyond schema.

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?

Description clearly states the tool shows endpoint, headers (masked), auth state, and schema cache state, with optional ping. Distinct from sibling tools that manage connections.

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?

Explicit guidance on when to set ping=true (to verify endpoint and measure latency). No explicit when-not-to or alternatives, but context is clear.

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