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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value beyond these by specifying the exact response shape in each state: 'authenticated:true' with 'empty pending[]' when connected, and 'connect_url' for toolkit/per-install URLs when credentials are missing. It could have mentioned the partially-connected/impending state explicitly, but the conditional detail is genuinely informative and consistent with 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?

Two sentences, front-loaded with the core purpose and packed with specific behavior. No filler words. Every clause serves a purpose, describing both the happy path and the missing-credentials path efficiently. Excellent conciseness.

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?

For a status-checking tool with no parameters and no output schema, the description covers the two primary states (all connected and missing credentials). The mention of 'pending[]' hints at a third partial state that is never explicitly described, which is a minor gap. Overall, it is complete enough for an agent to understand both invocation and response semantics.

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?

There are zero parameters in the input schema, and the schema covers 100% of params by default. Per the rubric, a 0-parameter tool starts at a baseline of 4. The description appropriately skips parameter details since none exist. Nothing more is needed.

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?

Uses a specific verb+resource: 'Returns connection status and URLs.' The description clarifies it's a status-checking endpoint despite the name 'connect,' distinguishing it from siblings like 'authenticate' (which likely initiates a flow). The behavior under two conditions (all connected vs. missing credentials) precisely scopes the tool's purpose.

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?

Clear usage context: the agent can infer this is the go-to tool when it needs to check whether providers are connected or obtain connection URLs. However, there is no explicit statement of when NOT to use it or which sibling to use instead (e.g., 'use authenticate to establish credentials'). The conditional flow descriptions provide actionable context.

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