Sync Metadata Cache

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

Annotations mark this as a non-readOnly, non-idempotent write, and the description corroborates by explaining it populates a local cache, that the cache lives 24h by default (MANTIS_CACHE_TTL), and the fallback tag-scanning strategy for MantisBT < 2.26. That is meaningful behavioral context beyond the annotations, though it never states that the cache is overwritten or that concurrent runs may interleave.

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?

Front-loaded with the core action, then layered with the fallback behavior and cache TTL. Every sentence carries information the agent would otherwise have to guess; no filler.

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 zero-parameter, no-output-schema mutation tool, the description covers what is fetched, where it goes, how tags are handled, TTL, and when to invoke it. The missing piece is orientation relative to the sibling metadata/list tools, which an agent needs to route correctly.

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 there is no parameter semantics to document and the baseline is 4. The description correctly adds no phantom parameter behavior.

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+resource: fetch projects/users/versions/categories/tags from MantisBT and write them into the local metadata cache. The read-then-store semantics are unambiguous. It does not differentiate itself from the sibling get_metadata / get_metadata_full tools, which is the only thing keeping it below a 5.

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?

"Use this tool to refresh stale data" and "useful for getting a complete overview" give clear positive usage context, and the 24-hour cache validity implies the refresh cadence. No alternatives or when-not-to-use conditions are named, so it stops short of a 5.

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