priority_dag_task_scheduler

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the cost ('0.030 USDC on Base L2') and implies a computational scheduling operation, but does not disclose whether it is read-only, has side effects, requires payment to execute, or what happens on failure. The cost is useful, but other behavioral aspects are missing.

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, information-dense sentence with the cost appended in parentheses. It front-loads the core purpose and is concise without redundancy. The cost is placed at the end, which is acceptable. It is appropriately sized for the tool's complexity.

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?

For a tool that handles complex DAG scheduling with concurrency and dependencies, the description lacks crucial context. There is no output schema, so the description should explain what the tool returns (e.g., a schedule, critical path length, errors). It also does not clarify how to structure the payload, what concurrency bounds mean, or how dependency tracking is represented. This is inadequate for an agent to use correctly.

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 coverage is 100% as both parameters are described, but the descriptions are generic ('Input parameters or JSON string payload' and 'Base L2 USDC micropayment signature'). The tool description hints that the payload should contain a DAG specification, but it does not explicitly detail the expected structure, fields, or constraints. This adds minimal value 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 states a specific function: 'Topological sort and critical-path scheduler' for 'complex agent task Directed Acyclic Graphs (DAG)'. This clearly identifies the verb and resource, and distinguishes it from sibling tools focused on other domains like mesh processing or crypto verification. However, it does not explicitly state the output format (e.g., a schedule order, critical path length), leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites, exclusions, or conditions. It simply describes the tool's purpose without context on selection criteria. This is a significant gap given the large sibling list.

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