start_morphologist

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool generates sulcal graphs but does not explain side effects, auth needs, or whether it modifies input data. Lack of detail on execution behavior limits transparency.

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, concise sentence (13 words) with no filler. However, it is overly minimal and could be expanded without losing conciseness to include more useful context.

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 four parameters, the absence of annotations or output schema details in the description, and no examples, the description is incomplete. It does not explain what the tool returns or how to configure it beyond the basic function.

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 0%, so the description must compensate. It only implies that 'input_dir' contains raw T1 MRI data, but does not explain other parameters ('output_dir', 'parallel', 'enable_sulcal_recognition') or their purposes. This is insufficient for correct invocation.

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 'Launch Stage 1: generate sulcal graphs with Morphologist from raw T1 MRI data.' It uses a specific verb ('Launch') and identifies the resource and output, distinguishing it from sibling tools like 'start_cortical_tiles' which target different stages or outputs.

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 versus alternatives (e.g., start_pipeline, start_cortical_tiles). The description does not mention prerequisites, exclusions, or context for selection, leaving the agent without direction.

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