manage_logs

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

With no annotations, the description carries the full transparency burden. It discloses key behaviors: clear does not reset sequence numbers, cursor mode returns logs oldest-to-newest with metadata. However, it omits whether clear is destructive or irreversible, and doesn't specify return values.

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 a single sentence that front-loads the core purpose ('Output logs') and enumerates capabilities compactly. While not bulleted, it is clear and avoids redundancy. Could be slightly improved with structured formatting.

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 no output schema and six parameters, the description explains actions and cursor behavior but lacks details on return values (e.g., what 'clear' returns, error handling). This leaves gaps for agents needing full response context.

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 coverage is 100%, but the description adds value by grouping parameters per action (e.g., level, limit, pattern for 'get') and specifying default limits (100 for get, 20 for errors). This context helps agents set appropriate values beyond the schema.

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 is for outputting logs and lists three distinct actions (get, clear, errors) with specific capabilities like filtered retrieval and cursor-based polling. This distinguishes it from sibling tools like manage_animation or manage_assets, which handle different domains.

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 when to use each action (e.g., 'get' for retrieval, 'clear' for buffer clearing), but provides no explicit guidance on when not to use this tool or alternatives. No mention of prerequisites or comparative usage with sibling tools.

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