MTA:SA Documentation MCP Server

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

No annotations are provided, so the description carries full burden. It states the action ('Clear') but does not disclose behavioral traits such as whether this operation is destructive, requires specific permissions, affects performance, or has side effects. The description is minimal and lacks critical context for a mutation tool.

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 a single, efficient sentence with zero waste. It is front-loaded with the core action and scope, making it easy to parse quickly without unnecessary elaboration.

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 annotations and no output schema, the description is incomplete for a mutation tool. It fails to explain what 'clearing cache' entails behaviorally, what the response looks like, or any error conditions. This leaves significant gaps for an agent to understand tool effects.

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?

Schema description coverage is 100%, so the schema already documents the parameter fully. The description adds marginal value by reinforcing the 'all' option, but does not provide additional syntax or format details beyond what the schema specifies. With 0 parameters needing extra explanation, a baseline above 3 is appropriate.

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 specific action ('Clear') and resource ('MTA:SA documentation cache'), with precise scope ('for a specific function or all functions'). It directly distinguishes from sibling tools that retrieve, list, or search functions rather than clearing 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 implies usage when cache clearing is needed, but provides no explicit guidance on when to use this tool versus alternatives or any prerequisites. It mentions the 'all' option, which hints at scope, but lacks context about effects or trade-offs compared to other tools.

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