docs_refresh

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

Annotations already declare idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds the behavior of reconnecting and refreshing available tools, but it does not disclose further behavioral details such as potential side effects, network dependencies, or what 'refresh' entails. With annotations present, the description offers minimal added behavioral transparency, consistent with a 3.

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 extremely concise: two sentences that front-load the action ('Reconnect... refresh...') and then provide the use case. Every word earns its place with no redundancy or filler.

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 simple maintenance tool with no parameters, an existing output schema absent, and annotations covering idempotency and safety, the description fully explains what it does and when to use it. The low complexity means this is complete information.

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 accepts zero parameters, and the schema is empty with 100% coverage. The description has no need to explain parameter semantics, and the baseline for zero-parameter tools is 4, so this score is appropriate.

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 purpose: to reconnect to SDK documentation and refresh available tools. It uses specific verbs ('reconnect', 'refresh') and names the resource (SDK documentation, available tools), which distinguishes it from siblings like docs_list_tools (which lists tools) and docs_health (which likely checks health).

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 gives explicit guidance on when to use the tool: 'Use if docs seem stale or unavailable.' This provides a clear context but does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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