logs

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether actions like 'clear' are destructive, whether 'start' begins a long-running process, or if authentication is required. The description is too brief to inform the agent of side effects.

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 short ('Manage session app logs.') but this is under-specification rather than efficient conciseness. A single vague sentence fails to provide necessary information. It should be expanded to include key details like available actions and typical usage.

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 (24 parameters, multiple actions, no output schema), the description is insufficient. It does not explain what the tool returns, how actions relate to parameters, or any prerequisites. A complete description would address these gaps.

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 input schema has high coverage (88%) with descriptions for most parameters. However, the tool description adds no additional meaning or context beyond the schema. For example, the 'action' parameter's enum values are not explained in the description. Baseline 3 is appropriate as schema does most of 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 'Manage session app logs' is vague. 'Manage' is a generic verb that could encompass viewing, starting, stopping, clearing, etc. The tool's action parameter includes specific operations like path, start, stop, doctor, mark, clear, but the description does not mention these, leaving the purpose unclear.

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?

There is no guidance on when to use this tool versus its siblings. Given that there are many sibling tools (e.g., boot, click, session), a description stating when logs is appropriate (e.g., 'Use this to start or stop log collection for a session') would be needed. Currently, no usage context is provided.

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