qbit_manage_logs

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

Although readOnlyHint=true already signals a safe read operation, the description adds meaningful behavior: get_documentation returns markdown text rather than JSON, get_logs returns in chronological order, and log_filename selects active vs rotated files. No annotation contradiction exists.

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 efficiently formatted as a bulleted list with signatures and brief, relevant details. The opening sentence is slightly generic, but every bullet earns its place by adding operation-level semantics.

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 wrapper/dispatcher tool, the description covers all operations, the argument-passing pattern, defaults, and the rotated-file distinction. The presence of an output schema reduces the need to explain return formats. Minor gap: it does not explicitly say 'arguments' can be omitted for operations that take no parameters.

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%, so the description carries the burden. It compensates by defining each operation's parameters (file, limit, log_filename) and their defaults, clarifying what the generic 'arguments' dict should contain. It does not fully specify value types, but the signatures are reasonably informative.

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 enumerates three specific operations with concrete verbs (Fetch, List, Fetch logs/documentation), which is more than a tautology. It does not explicitly contrast with sibling tools, but the operation names make its scope recognizable.

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 implies this tool is used for qbit_manage logs/documentation by listing its suboperations and the argument-passing convention. However, it never states when to choose this tool over sibling tools or when not to use it.

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