Read a bounded terminal transcript from an MCP-managed agent using its agent ID. Returns recent or visible output for orchestration and text inspection.
Read bounded terminal transcript from an MCP-managed Herdr agent. Use recent-unwrapped for orchestration-oriented text inspection.
| Name | Required | Description | Default |
|---|---|---|---|
| lines | No | ||
| source | No | recent-unwrapped | |
| agentId | Yes | MCP-managed persistent agent ID returned by agent_start. |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a bounded read operation but omits permissions, side effects, blocking behavior, error modes, and what 'bounded' means beyond the lines parameter.
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 short sentences, front-loaded with the core action and followed by a targeted usage hint. Every phrase adds value without padding.
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 3-parameter read tool with no annotations and no output schema, the description leaves important context unstated. It does not explain the meaning of 'lines,' the available source modes, or expected return shape, making it incomplete for reliable invocation.
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 only 33%, and the description only clarifies one enum value, 'recent-unwrapped.' It does not explain the other source modes, how 'lines' bounds output, or the default source behavior, so it only partially compensates for the schema gap.
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?
States a specific verb and resource: reading a bounded terminal transcript from an MCP-managed Herdr agent. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as read_file, process_read, or agent_get.
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?
Offers one source-mode hint, 'Use recent-unwrapped for orchestration-oriented text inspection,' but gives no guidance on when to choose this tool over sibling transcript/read tools. No when-not conditions or alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.