logs

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

There are no annotations, so the description carries the full behavioral burden. It discloses the timeout ('Times out after 90s') but does not explain side effects of actions such as clear, whether streaming requires explicit cleanup, what diagnostics or markers do, or what the response contains. For a tool with mutating actions, this is a significant transparency gap.

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 short and packs key information into a compact form. However, it is poorly structured: the final clause runs together as '...markers Times out after 90s,' which reads ambiguously and lacks clean sentence separation. It is concise but not well formatted.

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 18 parameters, 6 enums, no required fields, no output schema, and no annotations, the description is incomplete. It does not explain how actions relate to the many selectors, what combinations are valid, what the output looks like, or what the distinction is among path, start, stop, doctor, mark, and clear. An agent cannot reliably know how to invoke this tool correctly from the description alone.

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 high at 83%, so the baseline is 3. The description only loosely aligns with parameters: 'start/stop streaming' maps to start/stop actions, 'diagnostics' to doctor, and 'markers' to mark/clear. It adds no parameter-level detail beyond what the schema already provides.

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 the resource and main capabilities: 'Session app log info, start/stop streaming, diagnostics, and markers.' However, it lacks a main verb and is a noun-phrase list, so the agent must infer the actual operation. It also doesn't differentiate from sibling tools like events, trace, or perf, which could overlap with log/streaming functionality.

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 the tool: for session app log info, streaming, diagnostics, and markers. It also gives a useful constraint with 'Times out after 90s.' However, it never explicitly states when not to use it or which sibling tool to choose instead, leaving the agent to infer applicability.

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