treasury-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it indicates this is a read operation ('Get'), it doesn't disclose important behavioral traits such as whether this requires specific permissions, what format the stats are returned in, whether there are rate limits, or how current the data is. The description is minimal and lacks behavioral context.

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 perfectly concise - a single sentence that efficiently communicates the tool's purpose and what it returns. Every word earns its place, with no wasted language or unnecessary elaboration. The information is front-loaded and immediately understandable.

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 that this is a read-only tool with no parameters and an output schema exists, the description is reasonably complete for its basic purpose. However, with no annotations and multiple sibling tools that might overlap in functionality, the description could benefit from more context about when this specific quick stats tool is most appropriate versus other mempool analysis options.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, and it focuses on what the tool returns instead. This meets the baseline expectation for a zero-parameter tool.

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 ('Get quick mempool stats') and specifies the exact resources returned ('transaction count, size in bytes, min relay fee'), which distinguishes it from sibling tools like 'analyze_mempool' or 'get_mempool_ancestors' that likely provide different types of mempool analysis.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when this quick stats tool is appropriate compared to more detailed mempool analysis tools like 'analyze_mempool' or 'get_mempool_entry', nor does it specify any prerequisites or exclusions.

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