clear_output_log

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

With no annotations to supplement, the description carries the full burden of behavioral disclosure. It fails to mention any effects, side effects, or prerequisites, leaving the agent completely uninformed about what happens when the tool is invoked.

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 terse, but it under-specifies rather than being efficiently concise. It provides only an alias reference and no substantive information, so it fails to earn its place as a useful description.

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 tool has no annotations, no output schema, and only a minimal alias description. Given the existence of a sibling tool with a similar name, more context is essential to disambiguate and explain the tool's role, which is entirely absent.

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 tool has zero parameters, and the schema is empty with 100% coverage by default. Therefore, the description does not need to explain parameters, and the baseline of 4 is appropriate since no semantic gaps exist.

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 only states 'Alias for bridge_clear_log,' which does not convey what the tool actually does. It references another tool name without explaining the action or resource affected, leaving the purpose entirely dependent on external knowledge of bridge_clear_log.

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 provided about when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or context, making it impossible for an agent to decide between this and the similar bridge_clear_log sibling.

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