trajectory_record

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the tool never performs device actions, but it omits persistence behavior, auth requirements, idempotency/duplicate handling for action_id, and what the call returns.

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 a tight two-clause sentence with the core purpose and non-execution guarantee front-loaded. It contains no fluff, though it is arguably too terse for a tool with this many parameters.

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 16 parameters, no annotations, no output schema, and 0% schema description coverage, a single-sentence description is substantially incomplete. It communicates purpose and non-execution but leaves usage context, parameter semantics, and behavioral details unaddressed.

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 0% across 16 parameters, including 7 required fields and nested before/after/action objects. The description mentions only 'one externally executed action' and provides no meaning for task_id, action_id, timestamps, status enum, or other parameters.

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 a specific verb and resource: 'Record one externally executed action.' The clause 'never performs device actions' further distinguishes it from an execution tool. It does not explicitly differentiate from its siblings, but those siblings are unrelated stats/export tools.

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 phrase 'externally executed action' implies the tool is used after an action has already been performed elsewhere, and 'never performs device actions' clarifies what it should not be used for. However, there is no explicit when-to-use guidance, prerequisites, or comparison to alternatives.

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