linka-teach-stop

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

No annotations exist, so the description must bear the full burden. It only mentions 'confirmation and dry-run support' without explaining the behavioral implications (e.g., whether the recording is ended immediately, what happens to data, or error scenarios).

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 extremely concise but at the cost of being under-specified. It lacks crucial details needed for effective tool use, making it insufficient despite its brevity.

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 5 parameters, no output schema, and no required parameters, the description should provide substantive context about the stopping process, confirmation flow, dry-run behavior, and reason parameter. It fails to do so, leaving the agent with no guidance.

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%, yet the description adds no parameter-specific information. The vague mention of 'confirmation and dry-run support' hints at the purpose of some parameters but fails to clarify their meaning, constraints, or relationships.

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 states the action 'Stop' and the resource 'Teach recording', implying a stoppage of a recording session. However, it does not explicitly differentiate from sibling tools like linka-teach-start or linka-teach-status, which are distinct but without clear usage boundaries.

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 is given on when to use this tool versus alternatives, nor are there prerequisites (e.g., active recording) or hints about the context for using dry-run vs. confirmation.

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