Logger Debuglog

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

With no annotations, the description carries full behavioral burden. It usefully flags this as a write operation that generates diagnostic data, but adds nothing about the fact it is an async 'start' task, its duration, progress/cancellation behavior, required permissions, or overwrite semantics for output_dir.

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?

A single front-loaded sentence with parenthetical role cue; no filler. It is efficient, though it is under-specified rather than truly tight given what an async copy tool needs to convey.

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?

For a 6-parameter, annotation-free mutation/async tool, the description is thin: it omits async/cancellation behavior and any routing versus the export/diagnostic siblings. The presence of an output schema lowers the bar for return values, but the operational gaps remain.

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 100%, so all six parameters (host, port, scheme, profile, srv_type, output_dir) are already documented in the schema. The description adds no parameter-level meaning beyond that, which is the correct baseline when the schema does the work.

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 names a concrete verb+resource (start copying debug logs) and the destination (local directory), so the agent knows what the tool does. However, it never distinguishes itself from the very similar siblings logger_export and diagnostic_export, leaving overlap ambiguous.

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 when-to-use guidance and no alternatives are named, despite several plausible competing tools (logger_export, logger_clear, diagnostic_export, logger_archive_*). The agent must guess when this is preferred over exporting or archiving logs.

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