dev_pipeline_logs

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

Annotations already declare a safe read profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description still adds real value beyond them: logs may contain command output and there is no automatic secret scrubbing, a genuine security-relevant disclosure an agent should act on.

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 with the core action front-loaded and the safety caveat second. No wasted wording.

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 7-parameter tool with no schema descriptions and no output schema, the definition is too thin. It does not explain how logs are keyed, how to page via offset/maxBytes, or the relationship of attempt and device parameters, so an agent cannot call it precisely.

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?

There are 7 parameters with 0% schema description coverage, so the description carries the full burden and falls short. It never explains runId/nodeId selection, or the offset/attempt/maxBytes/deviceId/deviceName parameters, leaving pagination and device targeting entirely opaque.

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 (Read) and resource (bounded persisted node logs) with meaningful scope words 'bounded' and 'persisted'. It is distinguishable from siblings like dev_pipeline_status or read_process_output, though it does not explicitly name the pipeline family or contrast with them.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer from the resource noun alone that this retrieves logs for a pipeline node rather than live process output or pipeline status.

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