calculate_automation_score

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the calculation purpose and implies no side effects, but does not disclose anything about the input ranges, output format, or any constraints. An agent cannot predict what the function returns or how it behaves with varying inputs.

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 single concise sentence with no fluff, but it is under-specified for a tool with five parameters. It is well-structured in its brevity but fails to provide necessary context, making it merely a bare statement rather than an effective guide.

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 five required parameters and no output schema, annotations, or parameter descriptions, the description is severely incomplete. It does not explain the scoring scale, how to interpret results, or any prerequisites, leaving an agent largely in the dark about correct usage.

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% and the description makes no mention of the five required parameters, their meanings, or how they relate to the automation score. The parameter names (frequency, rule_clarity, etc.) are self-descriptive but the description adds zero value in interpreting them or their expected values.

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 states a clear verb (calculate) and resource (business process suitability for automation), distinguishing it from siblings like calculate_time_cost which focuses on cost. However, it does not specify the nature of the score or how it is derived, which slightly weakens differentiation but remains 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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it should be used when evaluating a process for automation, nor does it differentiate from calculate_time_cost or the create/save tools. No context or exclusions are provided.

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