compile_github_issue_rollover_bus

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

The description says the tool can optionally save an Anti-Permadeath Checkpoint into the Ghost Beacon Vault, which is a persistent write operation. The annotations declare readOnlyHint=true, directly contradicting that described behavior.

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?

The description is heavily padded with branding, author credits, fictional terminology, and example repositories before reaching the operational purpose. It is not front-loaded and contains substantial wording that does not help an agent decide or invoke the tool correctly.

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 complex tool with no output schema, it describes the main output as a ready-to-post Markdown Carry-Over Issue Header and mentions an optional checkpoint save. However, it omits return structure, error behavior, authentication requirements, and how the extracted data is formatted, leaving meaningful 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 100%, so the schema already documents issue_ref, tail_comments, michelin_token, and save_checkpoint. The description adds little parameter-level meaning beyond the schema and does not explain formats or constraints for those parameters.

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: it compiles a GitHub Issue rollover for issues approaching the 2,500-comment limit, extracting locks, QA defects, commit SHAs, and roster data into a carry-over header. The purpose is clear despite heavy jargon, though it does not explicitly distinguish this tool from any sibling tool.

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?

It gives clear usage context: multi-agent fleets operating inside GitHub Issues that are approaching the hard 2,500-comment limit. It does not name alternatives, exclusions, or when-not-to-use conditions, so it falls short of a 5.

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