Soxoa Automation Planner

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful context by emphasizing that results are illustrative, based on user-supplied assumptions, and not guaranteed or financial advice. This is useful behavioral nuance beyond the annotations.

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 two sentences with no filler, front-loading the core function and then adding a necessary caveat. Every sentence earns its place.

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 six parameters and zero schema descriptions, this description is too thin. It explains the high-level purpose but not how to choose or interpret parameters like automatableShare, implementationCost, or workingWeeks, nor the calculation basis behind the ROI estimate.

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 description coverage is 0%, so the description carries the burden of explaining parameters, but it mentions none of the six inputs. Even though parameter names are somewhat self-explanatory, the description adds no meaning beyond the schema's names, types, and bounds.

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 identifies the verb ('estimate') and the resource ('reclaimable team capacity and illustrative payback'), going beyond the name and title. It does not explicitly differentiate from the sibling tool prioritize_automation_workflows, but the distinct verb and outcome make the purpose understandable.

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 a clear intended use ('operational planning') and an explicit non-use ('not guaranteed savings or financial advice'). It does not name an alternative tool or provide when-to-use versus when-not-to-use comparisons, but the stated context is sufficient for basic routing.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it ranks and recommends, which is purpose rather than behavior, and doesn't mention any side effects or external impact. This is adequate but not additive beyond annotations.

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?

A single, front-loaded sentence that packs the action, scope, criteria, and output without filler. Every word contributes meaning, and the structure is easy to scan.

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 output schema exists and annotations cover safety, the description is mostly adequate for invocation. However, it lacks usage context relative to the sibling tool and does not clarify what 'discovery' means as a recommendation, leaving some ambiguity about the tool's full behavior.

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 description coverage is 0%, so the description must compensate for explaining parameters. It mentions criteria ('value, predictability, judgment, sensitivity, integration complexity') that map loosely to fields like weeklyHours and predictability, but it does not clarify value ranges, enum meanings, or how each field influences the rank. This is insufficient for a nested 1–12 workflow array.

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 a specific verb ('Rank') and resource ('user-described workflows'), plus the criteria and output recommendation types. It does not explicitly contrast with the sibling tool estimate_automation_roi, so it misses the differentiation needed for a 5.

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 implies the tool is for prioritizing workflows but gives no explicit guidance about when to choose this over estimate_automation_roi, nor any exclusion criteria. There is no 'when to use vs alternatives' information despite a sibling tool existing.

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