refresh

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

No annotations are provided, so the description must bear full behavioral context. It states the tool reloads from disk and requires a scope, but does not disclose side effects (e.g., temporary unavailability, idempotency, performance impact) or response behavior. The description is insufficient for an agent to fully understand the consequences of invocation.

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 a single sentence that front-loads the core action ('Reload the served index from disk') and includes a necessary requirement in parentheses. No extraneous words, making it highly concise and efficient for an agent.

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 the tool has a simple signature (1 required parameter, no output schema, no nesting), the description covers the basic action and a prerequisite. However, it does not explain what 'served index' means or what the tool returns after reload, which could leave gaps for an agent unfamiliar with the system.

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?

Schema coverage is 100%, with the single parameter 'token' described as 'bearer token (from TERO_TOKENS)' in the schema. The description adds no additional semantics beyond the schema, so it does not exceed the baseline score of 3.

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 'Reload the served index from disk' uses a specific verb and resource, clearly indicating a reload operation. However, it lacks context on what the 'served index' refers to, which could cause ambiguity without domain knowledge. It does not differentiate from siblings, but sibling tools are distinct in function.

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 mentions a required scope ('refresh' scope) but offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, appropriate contexts, or situations to avoid. Sibling tools like 'query_by_id' or 'text_search' have different purposes, but no explicit comparison is made.

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