variance_analysis__labor_efficiency_variance

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

With no annotations, the description carries the burden of disclosing behavior. It only provides a formula fragment without stating if it computes a variance, returns a number, or has side effects. Completely opaque.

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 short (one sentence) but not helpful. It lacks structure and context, making it cryptic rather than concise.

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 of a variance analysis tool with 3 parameters and no output schema, the description is woefully incomplete. It fails to explain the formula, expected output, or how parameters relate.

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 adds meaning for std_hours (defining it as standard hours allowed for actual output) but does not explain std_rate or act_hours. Schema coverage is 0%, so description partially compensates but insufficiently.

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 mentions 'variance-analysis' and 'std_hours = standard hours allowed for ACTUAL output', which hints at labor efficiency variance, but it's too vague to clearly distinguish from sibling tools like labor_rate_variance or material_usage_variance. The purpose is only partially conveyed.

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 other variance analysis tools. The description does not specify context, prerequisites, or when not to use it.

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