yade-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'pagination' (useful context for the parameter mechanism) and 'tracked' (suggesting filtered results), but fails to clarify sort order (implied reverse-chronological by 'skip_newest'), real-time vs. cached data, or what 'tracked' specifically means in the YADE 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?

The description is extremely concise at six words with no filler. It is front-loaded with the action verb. However, it may be overly terse given the lack of annotations and output schema documentation—it could accommodate one additional sentence covering usage guidelines without sacrificing clarity.

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 presence of an output schema, the description appropriately omits return value details. However, for a tool with no annotations and multiple task-related siblings, it lacks necessary context on what distinguishes 'tracked' tasks, the YADE system context, and how this listing relates to the task lifecycle (e.g., does it include completed tasks?).

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 100%, establishing a baseline of 3. The description mentions 'pagination' which contextualizes the limit/skip_newest parameters, but does not explain the unusual 'skip newest' semantics (reverse chronological ordering) or provide usage examples that would help an agent understand the pagination pattern.

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 action ('List') and resource ('tracked YADE tasks') and mentions pagination, which distinguishes it from a simple unconstrained list. However, it does not explicitly differentiate from sibling 'yade_check_task_status' (single task lookup vs. bulk listing) or explain what 'YADE' refers to.

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 is provided on when to use this versus alternatives like 'yade_check_task_status' for specific task lookups, or 'yade_execute_task' for creating new tasks. There are no stated prerequisites, exclusions, or workflow positioning hints.

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