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 mentions the tool analyzes git churn but fails to describe key behaviors such as output format (e.g., structured data vs. report), potential side effects (e.g., whether it modifies the repository), error handling, or performance considerations (e.g., timeouts for large histories). This leaves significant gaps for an agent to understand how the tool behaves beyond its basic function.

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 extremely concise and front-loaded, consisting of just two short phrases that directly convey the tool's function and prerequisite. Every word earns its place with no redundancy or unnecessary elaboration, making it efficient for quick understanding.

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 tool's complexity (analyzing git churn with metrics like volatility) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output contains (e.g., a list of files with metrics), how results are structured, or any behavioral nuances (e.g., handling of binary files). For a tool with no structured output documentation, this leaves the agent with insufficient context to use it effectively.

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 100% description coverage, with each parameter clearly documented (e.g., 'since_days' for time range, 'limit' for max results, 'file_pattern' for filtering). The description adds no additional parameter semantics beyond what the schema provides, such as explaining how 'volatility assessment' relates to these inputs. Given the high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 with specific verbs ('Per-file git churn') and resources ('commits, unique authors, frequency, volatility assessment'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_co_changes' or 'get_change_impact' that might also analyze git history, which prevents a perfect score.

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 implied usage guidance by stating 'Requires git,' indicating a prerequisite context. However, it doesn't offer explicit when-to-use guidance compared to alternatives (e.g., when to use this vs. 'get_co_changes' for change analysis) or any exclusions, leaving room for ambiguity.

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