refresh_entity

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Request and immediately perform a live refresh,' which implies an action but doesn't explain side effects, whether it's destructive, if it requires special permissions, how long it takes, or what the return value is. The behavior is vague and incomplete.

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, clear sentence with no redundant words. It front-loads the action and target, making it easy to parse. All information is relevant and efficiently presented.

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 mutation-like tool with no output schema and no annotations, the description is too sparse. An agent needs to know what happens after a refresh (response format? success/failure indicators?), whether the refresh is synchronous (it implies yes), and any prerequisites. The current description leaves critical operational details unspecified.

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 description coverage is 0%, leaving parameters undocumented. The description adds limited meaning by indicating entity_type can be 'department' or 'teacher,' but it doesn't specify exact accepted values, format, or how entity_id relates. It partially compensates for the schema gap but leaves ambiguity about valid inputs.

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 action (refresh) and the resource (department or teacher). It distinguishes this tool from siblings like search, get, compare, and rank by indicating a live update operation. The verb+resource combination is specific and unambiguous.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention conditions like stale data or the need to force a refresh, nor does it exclude usage when data is already fresh. The description offers no context on when a refresh is necessary compared to basic get/search operations.

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