trace-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. It effectively describes the core behavior (executes multiple tools, returns results for all calls) and mentions the performance benefit (reduces round-trips). However, it doesn't disclose potential limitations like execution order, error handling, or whether calls are executed sequentially or in parallel.

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 and well-structured in two sentences. The first sentence states the core purpose, the second provides usage guidance with concrete examples. Every word earns its place with no redundancy or 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?

For a batch execution tool with no annotations and no output schema, the description provides good context about what the tool does and when to use it. However, it doesn't describe the return format (though it mentions 'Returns results for all calls') or potential error scenarios, leaving some gaps in completeness.

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 fully documents the single 'calls' parameter with its structure, constraints (minItems:1, maxItems:10), and nested properties. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3.

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's purpose: 'Execute multiple trace-mcp tools in a single MCP request.' It specifies the verb ('Execute') and resource ('multiple trace-mcp tools'), and distinguishes itself from all sibling tools by being a batch execution mechanism rather than a single operation tool.

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 explicitly states when to use this tool: 'Use to reduce round-trips when you need several independent queries.' It provides concrete examples ('e.g., get_outline for 3 files, or search + get_symbol together') and implicitly distinguishes from alternatives by suggesting this is for multiple independent queries rather than single operations.

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