log-param

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

Description lacks important behavioral details such as whether logging a parameter overwrites or appends, what happens if the run does not exist, or any error conditions. With no annotations, the description should provide this context.

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?

Very concise single sentence, but could include more useful context without sacrificing brevity. There is room for a second sentence.

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 simple logging tool, the description should clarify behavior (e.g., idempotency, error handling). Without output schema, return behavior is unknown. Incomplete for an agent to use confidently.

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 67% (key and value have descriptions). Description adds no additional meaning beyond the schema. For runId, no description in schema nor clarification in tool description.

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 the tool logs a single parameter to a run, using a specific verb and resource. It distinguishes from siblings like log-metric and log-batch which log different types of data.

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 on when to use this tool versus alternatives such as log-batch or log-metric. No mention of prerequisites or when not to use it.

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