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

The description adds rich behavioral context beyond the annotations by explaining the response in different states: 'When all providers are connected' vs 'When credentials are missing'. It details what fields to expect (authenticated:true, pending[], connect_url) which is very helpful. This goes beyond the readOnlyHint and idempotentHint annotations, providing concrete behavioral expectations.

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 exceptionally concise, using exactly two sentences to convey both the primary purpose and the two most important execution states. Every clause adds value: the first sentence states the return type, and the second explains conditional outputs. No unnecessary words or repetition.

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 0-parameter, read-only status tool, the description provides a complete picture. It covers the main behavioral branches (all providers connected vs. missing credentials) and their corresponding outputs. No output schema exists, so the description appropriately explains return values. Given the simplicity of the tool, this is fully sufficient.

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, and the JSON schema correctly reflects this with an empty properties object, so schema coverage is trivially 100%. Per the rubric, 0 params gives a baseline of 4. The description does not need to explain any parameter semantics, which would be redundant here.

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's function with a specific verb and resource: 'Returns connection status and URLs.' It distinguishes itself from siblings by describing the output states (authenticated:true, pending[], connect_url) and is clearly different from 'authenticate' or 'show_version'. The scope is unambiguous and immediately conveys what the tool does.

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 for checking connection status but does not explicitly state when to use this over siblings or specify exclusions. No alternatives are mentioned, but the purpose is clear enough that a user can infer when this is appropriate. Lacks explicit guidance such as 'use this if you need to verify connectivity' or 'instead of authenticate'.

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