hevy_create_routine_folder

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

With no annotations, the description fully carries the burden. It discloses that the new folder is inserted at index 0, shifting existing folders, and details the dry-run mechanism. This gives agents necessary understanding of side effects.

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 efficient, starting with the core action and parameter, then explaining behavior and constraints in two sentences. No unnecessary words.

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 tool has one parameter, no output schema, and no annotations, the description covers the creation behavior, insertion index, and dry-run configuration. It lacks full response details for a successful write, but for a simple tool it is sufficiently complete.

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 confirms that 'title' is the only parameter and notes it's fixed after creation. However, it adds no additional semantic meaning beyond the schema constraints (e.g., uniqueness, format). With 0% schema coverage, the description compensates only modestly.

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 ('Create a routine folder') with the HTTP endpoint. It explicitly specifies that the only parameter is 'title' and distinguishes from siblings by noting there are no update or delete tools for folders.

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 provides usage context by explaining that the title is fixed after creation (no update/delete), implying caution. It also describes the dry-run behavior and how to enable writes via the environment variable, guiding when the tool actually performs writes.

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