run_seed

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Run seeders' without clarifying side effects, idempotency, or whether this is a mutation. The delegation to a command is not informative for behavioral traits.

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 very short (two sentences) but lacks structure and fails to front-load critical information. While not verbose, the brevity sacrifices completeness, making it only minimally adequate.

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 absence of an output schema and annotations, the description is incomplete. It does not explain return values, what happens when no seeder is specified, or whether the operation is safe to repeat. For a tool with several siblings, this is insufficient.

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% for the single parameter, meeting the baseline. The description adds no additional meaning beyond the schema, such as clarifying that omitting the 'seeder' parameter runs all seeders, or explaining the format of the seeder name.

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 'Run seeders' which is a clear verb+resource. It distinguishes the tool's function from siblings like 'run_migrate' or 'run_rollback' by focusing on seeding, though it does not explicitly differentiate from 'run_fresh' which also may involve seeding.

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 on when to use this tool vs alternatives like 'run_fresh' or 'run_migrate'. The description does not mention prerequisites, context, or exclusions, leaving the agent without clear direction on tool selection.

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