get_process_logs

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

With no annotations provided, the description must fully disclose behavioral traits. It notes capture timing and post-exit availability, but omits whether the operation is read-only, clears the buffer, or requires specific permissions. It does not describe side effects or limitations like rate limits.

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?

Two sentences efficiently convey core functionality. Remains concise without wasted words, though could be slightly more informative without increasing length (e.g., mentioning output format).

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?

Missing essential context: no description of return format (array of strings, objects?) despite lacking output schema. No differentiation from get_console_logs or get_event_log in terms of log type. Doesn't clarify if logs are continuous snapshots or one-time retrieval.

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% and description does not add any additional meaning beyond what the schema already provides for sessionId and tail. The description avoids mentioning parameters altogether, failing to enrich understanding of when to use tail or its default behavior.

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 identifies the tool as retrieving stdout/stderr output from an app process. It specifies the output is captured since launch and works post-exit, distinguishing it from siblings like get_console_logs (console messages) and get_network_log (network traffic).

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 explicit guidance on when to use this tool versus alternatives (e.g., get_console_logs for console messages, get_event_log for events). No mention of prerequisites like the session being from launch_app or context on 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.