Sync Metadata Cache

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

The description discloses the tag fetching fallback for older MantisBT versions and mentions that the cache has a default 24-hour validity (configurable via env var). Annotations are neutral, and the description adds value by explaining the caching behavior and endpoint dependencies.

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 concise, well-structured, and front-loaded with the main purpose. Every sentence contributes meaningful information about the fetching behavior, caching, and usage guidance without unnecessary verbosity.

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 the lack of parameters and output schema, the description provides a complete picture of the tool's functionality: what is fetched, how tags are handled, caching duration, and when to use it. It leaves no significant gaps in understanding the tool's behavior.

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 input schema has no parameters, so the description is not required to add parameter meanings. However, it provides context on what is fetched and how, which goes beyond the schema's minimal information. The baseline for 0 params is 4, and the description adds extra value, justifying a 5.

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 the tool fetches all projects and related metadata from MantisBT and stores them in a local cache. It distinguishes itself from siblings like 'get_metadata' by emphasizing the caching action and explains the fallback for tag fetching on older MantisBT versions.

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 indicates when to use this tool: to refresh stale data or get a complete overview of the MantisBT installation. It does not explicitly mention when not to use it or provide alternative tools, but the context of sibling tools implies that reading from cache is possible with 'get_metadata'.

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