Get Full Cached Metadata

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds valuable context: returns cached data, auto-syncs with a 24-hour TTL, and provides the complete raw metadata. No contradictions.

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?

Three concise sentences with no fluff. Front-loaded with the core purpose, followed by cache behavior and sibling guidance. Every sentence adds value.

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?

With no output schema, the description covers return content well. It explains the cached nature and auto-sync. Minor gap: no mention of data format (e.g., raw JSON structure), but it's sufficient for an agent to understand the output scope.

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 has no parameters, so the description correctly focuses on what it returns. Baseline for 0 parameters is 4; no additional parameter details are needed.

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 returns the complete raw MantisBT metadata cache with specific details (all projects, users, versions, categories, tags). It distinguishes itself from siblings by referencing get_metadata for a lightweight overview and sync_metadata for forced refresh.

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 advises when to use this tool (need complete raw metadata) versus alternatives (get_metadata for overview, sync_metadata for forced refresh). Also explains automatic sync behavior if cache is expired.

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