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

With no annotations provided, the description fully carries the behavioral burden. It explicitly declares the tool read-only and side-effect-free, notes that BotKelp never reads the user's repo, and states the account key requirement with sufficient credit. This gives an agent a clear safety profile.

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 front-loaded with the core purpose and side-effect declaration, then adds scheduling and auth requirements in dense, purposeful sentences. There is minimal redundancy; every sentence contributes useful information.

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 read-only check tool with only two parameters and no output schema, the description covers what it does, what input the agent must supply, how often it can be called, what side effects it does not have, and the authentication requirement. The output is also summarized (newer versions and CI freshness), so an agent can invoke it correctly.

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 coverage is 100%, so the input schema already fully documents both parameters. The description adds context like 'pinned' versions and 'pass the versions you currently have', but this largely restates the schema's own descriptions rather than adding substantial new meaning.

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 uses a specific verb ('compares') and names the exact resource (component versions pinned vs. BotKelp's registry), plus what it reports (newer versions and CI freshness). It also explicitly contrasts with writing or applying changes, distinguishing it from siblings like apply_changes_to_repo.

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?

Clear guidance is given for when to call it ('on whatever schedule you like — daily, weekly, on demand') and that it never pushes or applies changes. However, it does not explicitly name sibling alternatives or state when not to use it in favor of another tool.

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