calculate_lawn_mowing_frequency

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

No annotations are provided, so the description must carry the burden. It states the tool performs a calculation, implying a safe, read-only operation. However, it does not disclose any edge cases, side effects, or output specifics beyond the input schema.

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 extremely concise, using two short sentences. The first sentence presents the core purpose, and the second provides a helpful cross-reference. No wasted 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's simplicity (3 parameters, all described in schema, output schema present) and the low complexity of the task, the description provides sufficient context. It fully covers what the tool does and hints at related tools.

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 input schema has 100% description coverage, so the baseline is 3. The description simply lists the three parameters in terms matching the schema but adds no additional semantic nuance.

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 tool calculates a recommended lawn mowing interval using specific inputs (grass type, season, rainfall). It distinguishes itself from the many sibling calculation tools by focusing on a niche gardening task.

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 explicitly says 'Calculate recommended lawn mowing interval' and directs users to list_bundles for related 'jardinage' calculators, providing context for when to use this tool versus alternative garden calculators.

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