refresh_sprint_cache

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

The description discloses that the tool clears and re-fetches cache, which is behavior beyond the idempotentHint annotation. It doesn't mention any potential side effects like rate limiting or permission requirements, but for a cache refresh tool the description is reasonably transparent.

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?

Two brief sentences with the key action in the first sentence and usage guidance in the second. No wasted words; perfectly front-loaded.

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 cache refresh tool with an output schema, the description covers purpose and usage context sufficiently. It's simple enough that nothing more is needed.

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, so the schema is fully covered. The description doesn't need to add parameter-level details. The baseline of 4 applies because no parameters exist to document.

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 uses a specific verb phrase 'Clear and re-fetch the cached sprint info' which clearly distinguishes it from sibling tools like get_current_sprint by focusing on cache refresh. It also names the resource ('cached sprint info') exactly.

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?

Explicitly states when to use: 'when a sprint rolls over mid-session or if get_current_sprint returns stale data.' This gives clear context and references the alternative get_current_sprint, making the decision straightforward.

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