evolve_apply_curator_report

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

No annotations provided, so description must disclose behavior. It details automatic report selection, single-flight concurrency, and constraints on child actions (no code/git/PR). Does not cover error cases, but output schema may fill gaps.

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?

Three sentences front-loaded with purpose. Each sentence adds value without redundancy. Efficient structure for quick comprehension.

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 essential behavioral aspects for a single-parameter tool: purpose, parameter behavior, concurrency, and child action limits. Output schema likely handles return values. Minor gap: missing error handling, but acceptable.

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 0%, so description compensates by explaining the report_path parameter: optional, default behavior (picks latest REPORT-*.md), and directory reference. Adds meaning beyond schema's title and default.

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 'Apply a Curator advisory report' with a specific verb and resource. It distinguishes from siblings like 'evolve_apply' and 'evolve_apply_roadmap_issue' by focusing on curator reports.

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?

Provides clear guidance on when to omit the report_path (picks latest complete not already applied) and notes a single-flight constraint. Lacks explicit alternatives but context implies uniqueness.

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