record_run_observation

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

The description discloses a key behavioral trait—idempotency—and the unique composite key, which adds value beyond the tool name. However, with no annotations, it leaves out critical behavior such as what happens when the same key is reused with a different payload, whether it overwrites or errors, and any permission or side-effect implications.

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?

A single, front-loaded sentence with no redundant words. It efficiently communicates the essential idempotency and key structure, making every word earn its place.

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?

With no annotations, no output schema, and a terse description, the tool is under-specified. It lacks context about what constitutes an observation, expected payload format, duplicate handling, or return behavior, making it incomplete for safe autonomous invocation.

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 description states that run_id and observation_key form the key, giving relational meaning beyond the bare schema. It does not explain the purpose or structure of observation_payload, which remains undocumented, leaving a partial gap at 0% schema coverage.

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 identifies the action as recording an agent observation with an idempotency guarantee, keyed by run_id and observation_key. It specifies the resource and key structure, though it does not explicitly differentiate this tool from siblings like record_test_flow or capture_artifact.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of exclusions or prerequisites. The description only defines what the tool is, not when it should be invoked.

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