Sync Metadata Cache

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

The description adds valuable behavioral context beyond annotations: it explains the tag fetching strategy (dedicated endpoint vs scanning issues) and the configurable cache TTL via an environment variable. Annotations only indicate read/write safety but not these details.

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 well-structured with three clear paragraphs: purpose, technical detail, and usage guidance. It is front-loaded with the main action. Slightly verbose on tag fetching details, but overall concise enough.

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 no output schema and no parameters, the description covers the essential aspects: what it does, how it works (tag handling), and when to use it. It does not describe the return value, but that is acceptable for a side-effect tool.

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 no parameters, so schema coverage is trivially 100%. The description adds no parameter details, but none are needed. With zero parameters, the baseline score is 4.

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 that the tool fetches all projects and associated data (users, versions, categories, tags) from MantisBT and stores them in a local cache. It distinguishes itself from sibling read-only tools like get_metadata and get_metadata_full by focusing on refreshing the cache.

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 explicitly says 'Use this tool to refresh stale data' and explains the caching mechanism (24-hour TTL). It implies when to use, but does not explicitly contrast with alternatives or provide when-not-to-use scenarios.

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