create_macro_template

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

No annotations provided, so the description carries full burden. It mentions the optional side effect of assigning to all days of the week, but lacks disclosure about overwriting existing templates, required permissions, or any destructive actions. For a creation tool, more behavioral context is needed.

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 compact, front-loaded with the purpose, and uses a clear docstring format with bulleted arguments. Every sentence adds value with no redundancy.

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 6 parameters, no annotations, and an existing output schema (not described), the description adequately covers inputs and the optional side effect. However, it omits any description of the return value, error conditions, or uniqueness constraints on template_name, making it slightly incomplete.

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 coverage is 0%, but the description provides explicit docstring-style explanations for all 6 parameters, including units (grams, kcal), example values, and default behavior for assign_to_all_days. This fully compensates for the lack of schema descriptions.

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?

Description clearly states 'Create a new saved macro target template in Cronometer' with specific verb (Create) and resource (macro target template). It is distinct from sibling tools like list_macro_templates (listing), set_macro_targets (setting current targets), and set_weekly_macro_schedule (scheduling).

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; for example, it does not clarify when to use create_macro_template vs set_macro_targets or set_weekly_macro_schedule. The optional assignment to all days is mentioned but not linked to alternative scheduling tools.

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