generate_art_formula

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral aspects such as side effects, read-only nature, or permission requirements. The description focuses solely on output generation.

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 brief and well-organized, using a short introductory sentence and bullet-like notes. It avoids unnecessary verbosity while conveying the core purpose and important usage tips.

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 complexity (7 parameters, no output schema), the description lacks essential context such as what the generated formula looks like, how parameters interact, or what the return value is. This leaves ambiguity for the agent.

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 explains some parameters (date format, order, metric types) but leaves others like 'show_dates' and 'hide_weekends' unexplained. Coverage is partial; the description adds some value but does not fully clarify all seven parameters.

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 ('Generate') and the resource ('ART formula for Artemis Sheets'), and provides examples of use cases (prices, fees, revenue). It does not explicitly contrast with sibling tools, but the purpose is unambiguous.

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 practical notes (date format, order, metrics) but does not explicitly state when to prefer this tool over alternatives like get_artemis_data. The context is implied but not explicit.

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