create_gantt

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

With no annotations provided, the description carries the burden of behavioral disclosure. It covers the no-auth requirement, the scheduling behavior ('LoopGantt schedules it with its critical-path engine'), the outputs (picture, dates, critical path, link), and an explicit instruction to show the link. It does not mention error behavior or rate limits, but it is substantially transparent for this tool.

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 dense paragraph with no filler; key facts are front-loaded ('no account or API key needed') and each sentence contributes either usage context, authoring instructions, or output behavior. It is slightly long, but every clause adds value.

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 with no output schema, the description does explain the return value: a picture of the chart, dates, critical path, and a view/export/save link. It also covers the key task-authoring rules. It could be more complete by describing the returned image format or handling of invalid dependency references, but overall an agent has enough to call the tool 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 description coverage is 83%, so the schema already documents most parameters. The description adds meaningful authoring guidance: list tasks in execution order, use realistic working-day durations, use 0-based predecessor positions, and use { task, type, lag } for typed links or lag. This reinforces and extends the schema by explaining the expected mental model for creating a valid task list.

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 names a specific verb and resource: 'Create a Gantt chart from a task list.' It also clarifies the tool's scope (no account/API key, author a plan, critical-path scheduling). It does not explicitly contrast with siblings like schedule_project, so it falls short of full differentiation.

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 gives clear context on when to use the tool: when the user wants a Gantt chart, needs no authentication, and expects the agent to author a task plan. However, it never states when to prefer an alternative tool or exclude schedule_project/list_templates/get_template, leaving comparison to inference.

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