brain_begin

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

With no annotations, the description must fully disclose behaviors. It mentions creating a local gate file and optionally running senior_brief, but lacks details on idempotency, error states, permission requirements, or consequences of multiple calls.

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?

Two sentences, front-loaded with the core purpose. No fluff, every word earns its place.

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 5 undocumented parameters, the description is insufficient. It lacks return value info and per-parameter guidance, which are critical for correct usage.

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 description does not explain any of the 5 parameters. Schema coverage is 0%, so the description adds no meaning beyond parameter names like 'task', 'repo_id', etc.

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 starts a mandatory workflow for non-trivial tasks, creating a gate file. The verb 'start' and resource 'project-brain workflow' are specific. There are no other 'begin' siblings, so it distinguishes well.

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 indicates it's for 'non-trivial tasks' and optionally runs senior_brief, giving some context. However, it doesn't explicitly state when not to use this tool or provide alternatives like brain_finish for completion.

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