Refresh Sources

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

The description discloses that it fetches from 'all configured llms.txt URLs' and 'updates the local index,' which adds behavioral detail beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false). It also describes the return dictionary including counts and errors. No contradiction with 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 three concise sentences with the main verb phrase front-loaded. It efficiently conveys purpose, mechanism, and return value without redundant filler. Every sentence earns its place.

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-parameter trigger tool with an output schema, the description is complete. It covers the purpose, the scope ('all documentation sources'), the mechanism ('fetches from llms.txt URLs'), the side effect ('updates the local index'), and the return structure. No significant gaps remain.

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, and the schema coverage is 100% (empty properties). The description correctly omits any parameter details. The baseline for 0 params is 4, and the description adds no unnecessary param info, making it 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 opens with a specific verb+resource: 'Manually trigger a refresh of all documentation sources.' It distinguishes from siblings (search_docs, get_doc, get_doc_excerpt, list_sources) by clearly indicating a mutating refresh operation rather than a read or query operation.

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 states 'Use this when you need the latest documentation content,' providing clear context for when to invoke the tool. It does not explicitly list exclusions or alternatives, but the sibling tools are clearly different in purpose, and the usage guidance is sufficient for straightforward selection.

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