Gradle Dependency Version Checker

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

Annotations include readOnlyHint: true. Description reinforces read-only nature and adds behavioral details like known failures (e.g., wrong Coil group, missing BOM wrapper). No contradictions. Slightly above baseline due to additional context.

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?

Description is a single concise paragraph, front-loaded with purpose. Contains useful details but could be more structured (e.g., bullet points). Not verbose, but not maximally efficient.

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?

Tool has one parameter and no output schema. Description fully explains input examples and output format: 'latest stable version, ready-to-paste Kotlin DSL, BOM resolution, KMP vs Android distinction.' Sufficient for the agent to understand inputs and outputs.

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?

Input schema has one parameter 'library_name' with minimal description. The description provides extensive examples and contextual notes about expected values (e.g., 'compose', 'hilt') and return details (BOM, KMP distinction). This adds significant value beyond schema, but schema coverage is 100%, so baseline 3, justifying 4.

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?

Description clearly states it is a 'Live version lookup for any Android, Kotlin, or Jetpack library from Google Maven and Maven Central.' The verb 'lookup' and resource 'latest stable version' are specific. It distinguishes from sibling tools by focusing on dependency version checking.

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?

Explicit instruction: 'ALWAYS call this before adding or updating any dependency in build.gradle.kts.' Provides examples and known failures, aiding the agent in when to use. However, does not explicitly state when not to use or mention alternatives, so not a 5.

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