trace

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

The description is extremely minimal and does not disclose any behavioral traits beyond the core action. Without annotations, it fails to mention side effects, required permissions, or what happens during trace capture. The agent gains no insight beyond the action parameter.

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 very concise (5 words) but is under-specified rather than efficiently informative. It could be expanded slightly to include key behavioral context while remaining concise.

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 high parameter count (23) and no output schema, the description is far too sparse. It does not explain what trace capture entails, what output to expect, or how the many parameters affect behavior. The tool's purpose is stated but not elaborated enough for an agent 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?

Schema description coverage is 91%, so the input schema already documents most parameters well. The description adds no additional parameter meaning beyond what the schema provides. Baseline score of 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 states 'Start or stop trace capture,' which clearly identifies the verb ('start or stop') and resource ('trace capture'). It distinguishes the tool from siblings like 'record' or 'replay' by naming the specific action, but it does not explicitly differentiate from potential overlaps.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'record', 'replay'), nor any prerequisites or context for its invocation. The description gives no hints about appropriate scenarios.

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