pve_ceph_log

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

Declares the tool read-only and warns about output shape not being live-verified, which is useful transparency. With no annotations, the description carries the burden and handles it well, though more detail on rate limits or permissions could be added.

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?

Compact and front-loaded with key purpose, though the adversarial warning and shape note add density. No unnecessary sentences, but could be slightly more streamlined.

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?

Covers purpose, read-only nature, adversarial warning, and output shape uncertainty. Lacks mention of permissions or rate limits, but for a read-only log tool it is fairly complete.

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% with good parameter descriptions. The description adds the URL pattern but little extra parameter behavior beyond the schema, so baseline 3 is appropriate.

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?

Clearly states it reads Ceph log lines from a node ('Ceph log lines from a node'), distinguishes from sibling tools like pve_node_syslog and pve_node_journal by specifying the Ceph context.

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?

Provides an adversarial warning about treating output as data, not instructions, and indicates similarity to pve_node_syslog/pve_node_journal. However, lacks explicit guidance on when not to use this tool versus specific alternatives.

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