Server version

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

Annotations already mark readOnlyHint=true, but the description adds genuinely useful behavior: it makes no API call, never reports the API key or secret, and reveals the stale-cache caveat. These are exactly the behavioral facts an agent needs beyond the structured 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?

The description is compact yet complete, front-loads the tool's core purpose, and each sentence earns its place—including the warning about stale tool lists. No filler or repetition of schema details.

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 no-argument, read-only introspection tool with no output schema, the description fully covers invocation constraints, behavioral side effects, and the key context about cached tool lists. Nothing an agent needs to call it correctly is missing.

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, so the schema carries no semantic load. The description explicitly confirms it takes no arguments, which is all that is needed. This earns the baseline of 4 for a parameterless tool.

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 names a specific verb ('Report') and a precise resource: the CloudSee Drive connector version, registered tool count, and configured API host. This clearly distinguishes it from the file-operation siblings, which all act on files or buckets.

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?

It explicitly tells the agent to answer from the tool rather than from an assumed package version, and explains the stale-tool-list scenario that motivates this. This gives clear when-to-use guidance and prevents a common misuse.

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