trustmodel_trace_step

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

Discloses auto-assigned step numbers (1-based) and default timestamp. No annotations provided, so description carries burden; however, it does not detail error handling, side effects, or behavior for invalid trace_id.

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?

Three concise sentences, front-loaded with purpose. Every sentence adds value without redundancy.

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?

Covers main usage and required parameter, but does not explain return value or error scenarios. Given high parameter count (12) and no output schema, additional context about success/failure would improve 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 all parameters have descriptions. The description adds minimal extra meaning beyond the schema (e.g., step number auto-assignment). Baseline 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?

Description clearly states verb 'Record a single step' and resource 'active trace session'. Distinguishes from siblings (trace_start, trace_finalize) by specifying it is for step recording during an active session.

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?

Explicitly describes when to call ('once per reasoning step, tool call, tool result, or user-facing response') and prerequisite ('Requires a trace_id from trustmodel_trace_start'). Lacks explicit when-not-to-use or alternatives, but context is sufficient.

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