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

With no annotations and no output schema, the description carries the full burden, yet it only says it fetches logs. It discloses nothing about log format, pagination or truncation, retention window, permissions, or whether the environment must still exist. This is thin for an unannotated read tool.

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?

A single short, front-loaded sentence with no wasted words. It is efficient, though its brevity is more under-specification than disciplined concision.

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 two-required-parameter tool with zero annotation coverage, no output schema, and 0% schema descriptions, the definition is incomplete. An agent cannot tell how the ids relate, what a log payload looks like, or what failure modes to expect.

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 0% and both required parameters (workflowJobId, bnsEnvironmentId) are completely undocumented in the description. The description adds no meaning about which job id to use or why the environment id is required.

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 ('fetch logs for a BunnyShell workflow job'), which cleanly separates it from list-bunnyshell-workflow-jobs and get-workflow-execution. It does not, however, name or distinguish itself from the most adjacent siblings, so it falls short of a 5.

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?

The 'Troubleshooting:' prefix hints at the intended scenario (diagnosing a failed/hung job) but gives no explicit when-to-use vs when-not, and never names an alternative sibling such as get-last-run-workflow-detail. Usage is only implied.

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