lerobot_job_logs

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

The description does not disclose behavioral traits beyond the basic action. 'Tails' implies limited output, but there is no mention of permissions, prerequisites (e.g., job completion), error handling, or output format. Annotations are absent, so the description carries the full burden but fails to provide sufficient transparency.

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, front-loaded sentence that precisely conveys the tool's purpose without any extraneous words. Every word is necessary and earns its place.

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?

Despite the tool's simplicity (1 parameter, output schema exists), the description is incomplete for an agent. It lacks context on how logs are retrieved (e.g., job completion needed), output format (though schema may help), and integration with sibling tools. The agent would need additional knowledge to use it effectively.

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 parameter 'job_id' is a required string with 0% schema description coverage. The description adds no meaning beyond the schema, such as format, examples, or constraints, leaving the agent without guidance for correct invocation.

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 it returns stdout and stderr tails for a background job, using a specific verb and resource. It is distinct from sibling tools like 'lerobot_job_status' (status) and 'lerobot_list_jobs' (listing), though it doesn't explicitly differentiate.

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 guidance is provided on when to use this tool versus alternatives such as 'lerobot_job_status' or 'lerobot_list_jobs'. The description only states what it does, with no context for tool selection.

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