Refresh Sharing Group

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context that it affects the cached index, but does not describe side effects, required permissions, failure modes, or what exactly 'refresh' entails. 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 a single, well-structured sentence that is front-loaded with the action and object. No unnecessary words 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?

For a low-complexity tool with one parameter and annotations, the description is minimally adequate. However, it lacks context on when to use it versus the similar sibling replenish_indexes or what outcomes to expect, leaving some ambiguity for an agent.

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 only parameter group_id is fully described in the schema as 'Sharing group id'. The description adds no extra semantic meaning beyond the schema, which has 100% coverage, so the baseline of 3 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 'Refresh a sharing group's cached shared-resource index' clearly states the action (refresh) and the specific resource (sharing group's cached shared-resource index). It distinguishes itself from other sharing tools like get_group or update_group by focusing on cache refresh.

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 implies usage is for refreshing cached indexes but gives no explicit when-to-use guidance or alternatives. It does not differentiate from the sibling tool reconcile_indexes or explain when a refresh is needed.

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