clear_request_logs

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

Annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds valuable context: it specifies the permanence of removal ('Permanently remove'), the scope ('all captured request/response logs'), and the irreversible nature ('cannot be undone'). This enhances understanding beyond the annotations without contradicting them.

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 front-loaded with the core action, followed by usage context and warning, all in three concise sentences with zero wasted words. Each sentence earns its place by providing critical information efficiently.

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's complexity (destructive, no parameters, no output schema), the description is complete: it covers purpose, usage guidelines, behavioral traits (permanence, irreversibility), and parameter implications. With annotations providing safety hints, no additional details are needed for effective agent use.

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 parameters and 100% schema description coverage, the baseline is 4. The description appropriately explains that no inputs are needed, as it removes all logs by default, which aligns with the empty input schema and adds semantic clarity.

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 specific action ('Permanently remove') and target resource ('all captured request/response logs'), distinguishing it from siblings like 'get_request_logs' (which retrieves logs) and 'reset_verification' (which resets verification state). The verb 'remove' is precise and unambiguous.

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?

Explicit guidance is provided on when to use this tool ('for test isolation between test runs') and when not to use it ('This action cannot be undone'), with clear alternatives implied (e.g., use 'get_request_logs' to view logs instead). This helps the agent choose appropriately between destructive and non-destructive operations.

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