serial_clear_history

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

The description adds behavioral details beyond the annotations: it says 'Resets the read cursor and frees memory,' which aligns with the destructiveHint=true and readOnlyHint=false. The idempotentHint=true is supported by the reset behavior. No contradictions with annotations.

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 concise: one sentence for the action, one for the effects, and a short usage note. The 'Args' section is structured and front-loaded. Every sentence earns its place with no redundancy.

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 the tool has no output schema, the description does not mention return values or success/failure indicators. For a destructive tool, explaining the resulting state (e.g., buffer cleared) would improve completeness. However, it covers the main action and usage well.

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?

With 0% schema description coverage, the description adequately explains the single parameter: 'session_id: Port name of the session. Optional if only one session is open.' This adds meaning beyond the schema, which only defines type and default. It clarifies the parameter's purpose and optionality condition.

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 tool's action: 'Clear the receive history buffer for a session.' It uses a specific verb ('Clear') and resource ('history buffer'), and the addition of 'Resets the read cursor and frees memory' further clarifies what the tool does. Among sibling tools, this is distinct from other operations like reading, writing, or opening/closing sessions.

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 description provides explicit usage context: 'Useful for long-running sessions on chatty devices, or to get a clean slate before a new interaction.' This helps the agent decide when to invoke the tool. While it doesn't mention when not to use it or provide alternatives, the given context is sufficient for most cases.

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