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

The description states 'Running it successfully also marks the connection healthy in the user’s Datavrn settings', which is a side-effect write. However, annotations declare readOnlyHint=true, meaning no writes. This is a direct contradiction between description and annotation, making it impossible for the agent to trust either.

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?

Three sentences, front-loaded with the primary purpose, followed by usage guidance and side-effect disclosure. Every sentence earns its place, with no extraneous information.

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 no parameters and no output schema, the description comprehensively explains what the tool returns: organization, access profile, and next step. It also mentions the side effect, making it contextually complete for an agent to decide when and how to use it.

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, so there is nothing to explain. Per baseline for 0 params, a score of 4 is appropriate; the description adds no parameter details but doesn't need to.

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 identifies the tool as a connection verification utility, using specific verbs 'Confirm' and 'report' on the 'Datavrn connection' resource. It distinguishes itself from sibling tools by focusing on connection status and capabilities, not data operations.

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?

Explicitly states when to use: 'Call this first — or whenever the user asks whether Datavrn is connected'. This provides clear direct guidance and implies it is the appropriate tool for connection checks, with no ambiguity.

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