dm_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 mentions the choice constraint but does not disclose side effects, idempotency, permissions, or what happens when the choice is invalid or the record already exists.

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 short and front-loads the purpose before listing inputs. The dense input notation is efficient, though it sacrifices some readability.

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?

The output schema exists, so return values need not be explained. The description covers the essential input fields and a validation rule, but for a mutation tool with no annotations and a generic payload schema, it omits important behavioral context such as side effects and failure handling.

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 schema exposes only a generic payload object with 0% description coverage, so the description adds meaningful detail by naming decision_id, choice, and teacher_cost, marking two as required, and constraining choice to allowed_options. However, it still does not explain teacher_cost, decision_id, or the payload wrapper, leaving partial compensation for the schema gap.

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 says 'Record the teacher's choice,' which gives a specific verb and resource rather than restating the tool name. It does not differentiate this tool from close siblings such as dm_decide or do_record, so it falls short of a 5.

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 explicit guidance on when to use this tool instead of alternatives, nor any stated prerequisites. The phrase 'Record the teacher's choice' implies it follows a decision, but the agent must infer that context.

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