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 describes what information the tool provides (top imported files, PageRank-based connections, language stats, example tool calls) but doesn't mention response format, data freshness, permissions required, or any limitations. It adequately conveys this is a read-only informational tool but lacks operational details.

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 with two sentences: the first explains what the tool shows, the second provides clear usage guidance. Every word serves a purpose with zero redundancy or filler content.

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 zero-parameter informational tool with no output schema, the description provides sufficient context about what information will be returned and when to use it. It could be more complete by mentioning the response format or data scope, but given the tool's simple nature, it's adequately informative.

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 baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's purpose and usage context.

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 as an 'onboarding helper' that shows specific data types (top imported files, most connected symbols, language stats, example tool calls). It distinguishes itself from sibling tools by focusing on initial project exploration rather than analysis, refactoring, or querying operations.

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 explicit usage guidance: 'Call this first when exploring an unfamiliar project.' This gives clear temporal context (first) and situational context (unfamiliar project), distinguishing it from all sibling tools which serve different purposes like analysis, refactoring, or querying.

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