badgr_logs

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

With no annotations, the description carries the full burden but discloses nothing behavioral: no indication of whether the call blocks until completion, whether logs are tailed or truncated, how large a payload to expect, or whether the deployment must still be live. Only the schema hint that deployment_id comes from badgr_run/badgr_serve adds any operational context.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity reflects under-specification rather than tight editing.

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?

A single-parameter read tool with a fully documented schema, so the core invocation is answerable. But with no output schema and no annotation coverage, the description should say something about what logs come back and in what form; that gap leaves it merely adequate.

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 100% and the single parameter is documented with its provenance (returned by badgr_run or badgr_serve). The description adds nothing beyond the schema, so baseline 3 applies.

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 (Fetch) and resource (logs) scoped to a Badgr deployment, which is clear on its own. However, it never distinguishes this from sibling tools like badgr_status or badgr_down, which an agent must guess between when diagnosing a deployment.

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 on when to use this versus badgr_status (health) or badgr_down (teardown), and no prerequisites such as the deployment needing to exist or be running. The agent is left to infer that logs are only meaningful after badgr_run/badgr_serve.

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