Sync Metadata Cache

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

Annotations say readOnlyHint=false, idempotent=false and destructiveHint=false; the description explains that it writes to a local cache valid for 24h, consistent with that profile. It additionally discloses a cost/failure mode an agent could not infer: on MantisBT < 2.26 the tag endpoint is absent and tags are collected by scanning all issues across all projects.

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 deprecation warning, which is the most important information. Slightly redundant tail: "This is useful for getting a complete overview…" and "Use this tool to refresh stale data" restate what the preceding sentences already cover.

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, side-effecting cache-population tool with annotations covering the safety profile, the description covers scope, staleness policy and the legacy-installation fallback. The one gap is that it never says what the call returns (counts, confirmation, errors) and no output schema exists to cover that.

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 no parameters, so the baseline is 4; there is no parameter semantics to add. The description's mention of MANTIS_CACHE_TTL is useful context but is an environment variable, not a tool argument.

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 and resource: fetch projects plus their users, versions, categories and tags from MantisBT into a local metadata cache. The deprecation notice names the replacement (get_metadata with refresh: true), so an agent can route away from it immediately.

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 says when to use it ("Use this tool to refresh stale data") and when not to (deprecated, superseded by get_metadata with refresh: true). It also gives the cache validity window and the MANTIS_CACHE_TTL override, which determines whether a refresh is needed at all.

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