refresh_problem_statements

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

With no annotations, the description carries the full burden and does disclose two useful traits: the tool performs external network I/O against sih.gov.in and it mutates cached state with a 6-hour TTL. It says nothing about latency, failure behavior if the site is unreachable, whether concurrent calls are safe, or whether a refresh can degrade existing results.

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?

One sentence, front-loaded with the action, with the operational caveat in a compact parenthetical. Nothing wasted.

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 simple zero-parameter cache-refresh tool this covers what it does and the cache lifetime, which is the key decision input. Missing only the return/latency expectations that would matter since there is no output schema.

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 tool takes zero parameters, so the baseline is 4. The schema is empty and nothing in the description is needed to explain 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?

States a specific verb (re-download) and resource (problem statements) plus the source domain, which distinguishes it cleanly from the read-only siblings search_problem_statements, get_problem_statement, and list_facets. It stops just short of a 5 because it doesn't explicitly frame itself as the cache-invalidation counterpart to those reads.

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 parenthetical about the cache lasting 6 hours implies when a refresh is warranted, but the agent must infer that guidance. There is no explicit 'use this when data may be stale' or 'do not call more than once per session' instruction.

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