calculate_drain_slope

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

No annotations provided, and the description fails to disclose any behavioral traits (e.g., side effects, permissions, or whether it's a pure computation). It only mentions return values.

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 short but includes inaccuracies that reduce its effectiveness. It front-loads purpose but then misrepresents inputs.

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?

With only 2 parameters, the description should accurately guide parameter usage. It fails to explain the required fixture_type and how it affects calculation, and mentions missing inputs.

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?

Although schema coverage is 100%, the description introduces misleading inputs (pipe length, application) that don't align with the actual parameters (pipe_diameter_mm, fixture_type). This adds confusion rather than value.

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 it computes drain slope for plumbing code, but mentions non-existent inputs (pipe length, application) that don't appear in the schema. This inaccuracy undermines clarity.

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?

Only a vague 'Use for plumbing or roof drainage' is given. No explicit comparison to sibling tools like calculate_pipe_flow_rate or when not to use, despite many similar calculators.

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