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

With no annotations, the description carries the full burden and does it well. It openly discloses the narrow scope (workflow + update-automation hygiene only), what it does not check, that no API key is required, and that it returns a 'safe summary' with report URL. It also addresses privacy handling for private repos.

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 main purpose and each sentence adds useful information, but it is a dense paragraph. It could be broken into bullet points, yet it remains readable and earns its length given the scope caveats.

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, the description clearly explains what the user will receive (findings by category, counts, unlisted report URL, fix options). It also covers limitations, prerequisites (no API key), and private-repo handling, making it complete for a simple one-parameter tool.

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?

The schema already provides 100% coverage for the single `repo` parameter, so the baseline is 3. The description adds value by reinforcing the public-repo restriction and explaining how to handle private repos, which goes beyond the schema's text.

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 clearly states the tool scans public GitHub repos for GitHub Actions and CI security/maintenance hygiene, with a specific use case ('before launch' for AI-built apps). This distinguishes it from the sibling bounty tools, which are all about bounty management.

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?

Provides explicit when-to-use context ('before launch', 'ideal for apps built with Lovable, Bolt, Replit, Cursor, or v0'), explicit when-not-to-use (does not check secrets, auth, etc., and not for private repos), and an alternative (running `npx taskbounty-check .` locally for private repos).

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