list_gradle_tasks

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

The description states it runs 'gradlew tasks' which is a read-only operation, implying no destructive side effects. However, since there are no annotations provided, the description should ideally be more explicit about non-destructive behavior, output format (plain text), and potential prerequisites (e.g., Gradle installation). The description is adequate but not exhaustive.

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 a single sentence with a key parenthetical tip. It is front-loaded with the core purpose and efficiently conveys essential usage nuance without extraneous words.

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 no output schema and moderate parameter count (4), the description adequately covers the tool's purpose, scope, and a key parameter usage (task for submodules). It does not detail return format (text output) or behavior when no task is specified, but the core use case is well-served. A sibling reference to list_gradle_projects adds helpful context.

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 has 100% description coverage for all four parameters, so the baseline is 3. The description adds extra value by explaining the 'task' parameter's special usage for submodule scoping, which is not fully detailed in the schema. Additionally, it clarifies that 'json' is ignored by this tool, providing useful semantic nuance beyond the schema.

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 it lists available Gradle tasks via 'gradlew tasks' to discover build/test/install targets. It also distinguishes the scope (root project vs. submodule), which helps differentiate from sibling tools like list_gradle_projects or list_gradle_variants.

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?

The description explains when to use this tool (discover Gradle tasks) and provides a concrete alternative approach for multi-module builds (passing task="<module>:tasks"). It could be stronger with explicit when-not-to-use scenarios, but the sibling context and tip cover key usage guidance.

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