start_auto_refresh

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently indicates the conditional behavior ('if it's not already running') and notes that it is a manual override for an otherwise automatic process. However, it does not mention what happens if the system is already running (e.g., no-op, error) or describe the output/return value, so it is not a full 5.

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 two sentences, front-loaded with the core purpose in the first sentence and contextual guidance in the second. Every sentence earns its place, with no fluff 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?

Given that this is a simple, zero-parameter control action with no output schema, the description is sufficiently complete. It explains what the tool does, why it might be needed, and when to use it, making it self-contained for an agent to decide invocation.

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, so the baseline is 4 according to the rubric. The description adds no parameter-specific information (none needed), but it compensates by explaining the tool's purpose and context, making it clear that no inputs are required.

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: 'Manually start the auto-refresh system if it's not already running.' It specifies the verb (start), the resource (auto-refresh system), and a condition (if not already running), which distinguishes it from sibling tools like stop_auto_refresh and get_auto_refresh_status.

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 explicitly provides guidance on when to use and when not to use the tool: 'This is typically not needed as auto-refresh starts automatically with the server, but can be useful for recovery scenarios or manual management.' This clearly differentiates it from alternatives and gives concrete use cases.

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