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

Despite lacking explicit annotations about side effects, the description discloses clear behavioral outcomes: returns authenticated:true with empty pending[] when all providers are connected, and connect_url when credentials are missing. This adds meaningful transparency beyond the readOnly and idempotent hints.

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 concise, using only two sentences to convey the tool's purpose and key behavioral cases. No redundant or extraneous information is included.

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?

The description covers the two main scenarios but omits potential edge cases (e.g., partial provider connectivity or error states). Given the tool's simplicity and lack of output schema, this is mostly complete but could be slightly more thorough.

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 schema covers 100% of the interface. Since there are no parameters to explain, the description fully aligns with the schema and adds no unnecessary details.

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 the tool returns connection status and URLs, specifying the exact output in two distinct scenarios (all providers connected vs. missing credentials). The verb 'Returns' is explicit and the scope is well-defined.

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 does not provide any guidance on when to use this tool instead of siblings like 'authenticate' or 'marketplace'. It explains behavior but fails to indicate the appropriate context, such as checking status before authentication.

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