gradle-get-details

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering key behavioral traits. The description adds 'full output' but doesn't elaborate on truncation via maxChars or summaryOnly options, or on rate limits.

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?

Single 8-word sentence is very concise and front-loaded. However, it omits useful details that could be included without exceeding reasonable length.

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?

Given the complexity (5 parameters, no output schema), the description does not explain return values or how to interpret output. It lacks details on how summaryOnly, maxChars, and previewChars affect behavior, making it incomplete for effective use.

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?

With 60% schema coverage, 2 parameters (id, detailType) lack schema descriptions. The description does not mention any parameters or their meaning, failing to compensate for missing schema explanations.

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 the tool fetches full output for a previous build/test by ID, using 'Fetch' as the verb and 'full output' as the resource. It distinguishes from sibling tools like gradle-build (creates builds) and gradle-list (lists builds), but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives (e.g., gradle-list, gradle-test). The description implies you need an ID but doesn't specify prerequisites or scenarios where other tools are more appropriate.

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