as_gradle_run_task

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

Annotations already indicate destructive=true. Description adds context that it's a 'power tool' and 'escape hatch', and outlines return format (JSON with status, output, build outputs). Does not contradict annotations.

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?

Two clear sentences plus args/returns list. Front-loaded with purpose and guidelines. No fluff.

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?

Covers purpose, usage, and return format. Could mention potential duration or error handling, but timeout is in schema. Output schema exists, so return details are covered.

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 0%, but description lists the four parameters (project_dir, tasks, args, timeout) with brief hints. However, schema already provides detailed descriptions and types for each field, so description adds minimal extra 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?

Clearly states verb 'Run', resource 'Gradle tasks', and scope 'arbitrary with optional extra args'. Distinguishes from sibling dedicated tools like assemble/test/lint/clean.

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?

Explicitly tells when to use (escape hatch for tasks not covered by dedicated tools) and when not to (use dedicated tools when possible). Provides concrete examples like installDebug.

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