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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing via 'list', but it does not disclose pagination behavior despite a 'page' parameter, authentication/permission requirements, rate limits, or what the returned job records contain.

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 filler. It is appropriately sized for a simple listing tool and contains no unnecessary repetition.

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 listing tool with no annotations, no output schema, and zero schema descriptions, the definition is too thin. It omits pagination behavior, return contents, and differentiation from the sibling log retrieval tool, leaving an agent with significant gaps.

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% for two parameters. The phrase 'for an environment' loosely maps to the required bnsEnvironmentId, but the parameter is not named or explained, and the optional 'page' parameter is not mentioned at all, so the description does little to compensate for the schema gap.

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: 'list BunnyShell workflow jobs', scoped 'for an environment'. This is clear and not tautological, but it does not explicitly distinguish itself from closely related siblings such as get-bunnyshell-workflow-job-logs or list-workflow-executions.

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 gives only a vague contextual cue. There is no guidance on when to use this tool rather than get-bunnyshell-workflow-job-logs, list-workflow-executions, or get-workflow-execution, and no prerequisites or exclusions are stated.

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