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

Annotations already declare readOnlyHint:true and idempotentHint:true, which is consistent with the description's status-reporting nature. The description adds value by explaining the conditional behavior (when providers are connected vs. when credentials are missing), which goes beyond the annotations. It discloses that the tool returns different payloads based on connection state, which is useful for the agent to interpret the response.

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 two sentences, compact and information-dense. The first sentence summarizes the output, and the second explains the behavior when credentials are missing. No wasted words; every sentence contributes to understanding the tool's purpose and response. It is well-structured for quick comprehension.

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 that this is a status-checking tool with no parameters, no output schema, and rich annotations (readOnlyHint, idempotentHint), the description is complete. It explains the key states (connected vs. missing credentials) and what fields to expect. It does not need to describe return formats further because there is no output schema, but the description covers the essential scenarios. The tool is simple enough that no additional context is required.

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 zero parameters, and the schema is empty with 100% coverage (since there are no properties). The description correctly focuses on the behavior and return values rather than parameters. Since there are no parameters to explain, the description fully compensates by explaining what the output will be in different scenarios, making this dimension a perfect score.

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 clearly states that the tool returns connection status and URLs, which distinguishes it from sibling tools like 'authenticate' (which presumably initiates authentication) and 'marketplace' (which likely lists integrations). It specifies what information is provided (authenticated flag, pending array, connect_url, per-install URLs). However, it could be more explicit about what 'connect_url' is for and how it relates to the authentication 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?

The description implies usage: call this tool to check connection status, especially to see if all providers are connected or to get URLs for missing credentials. It does not explicitly state when not to use it (e.g., when you need to initiate connection), but the context with sibling tools suggests it's for status checking, not action. The mention of 'pending[]' and 'authenticated:true' gives clear context for typical usage.

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