Check the RoofScope connection

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing that this validates two separate credentials (API key and Scope API Token) plus an ordering flag — which explains its role as a failure-diagnosis tool. It does not, however, describe the response shape or how to interpret a failure, leaving a gap.

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 tight sentences: the first front-loads what is checked, the second gives the usage condition. No filler, no repetition of the title or annotations.

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?

With no output schema, the description carries the burden of explaining results, and it only implicitly conveys that the output reflects the three checks. It never says whether failures surface as errors or structured status fields, which is the main missing piece for a diagnostic tool an agent may call programmatically.

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 takes zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify, and it correctly avoids inventing parameter discussion.

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?

States a specific diagnostic action and enumerates exactly what it verifies: acceptance of the server's API key, the account's Scope API Token, and whether ordering is enabled. This is clearly distinguishable from the data-fetching siblings (search_roofscope_scopes, get_roofscope_prices, etc.), which return domain data rather than connection state.

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?

Gives a clear triggering condition: 'Use it when another RoofScope tool fails, or to confirm the setup.' That is actionable routing guidance. It stops short of an explicit when-not (e.g., not needed for routine data calls), so it is clear context rather than full when/when-not coverage.

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