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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: no indication of log volume, ordering, truncation, or whether logs are available only for finished jobs, which is exactly the kind of context a log-fetch tool should supply.

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 front-loaded sentence with no padding or repetition; the purpose and the usage cue both land immediately. Its brevity is efficient from a structure standpoint, even though the same terseness is penalized under completeness.

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?

With no output schema, four parameters (two of them required and undocumented), and no description of what the returned logs contain, this definition is not sufficient for reliable invocation. An agent cannot determine where to obtain bnsEnvironmentId or workflowJobId, or what to expect back.

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 50%, and the two documented parameters (botId, projectApiKey) are QA-bot plumbing rather than the tool's core inputs. The two required parameters, workflowJobId and bnsEnvironmentId, are undocumented in both the schema and the description, and the description provides no compensating detail about their format or source.

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 states a specific verb and resource: fetch logs for a BunnyShell workflow job. That is clear and unambiguous, but it never distinguishes itself from nearby siblings such as list-bunnyshell-workflow-jobs or get-workflow-execution, leaving the agent to infer which one returns logs.

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 is the only usage cue, implying the tool is for diagnosing a failed or stuck job. It names no alternatives, no prerequisites beyond the required IDs, and no condition under which another sibling should be preferred.

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