propeller_bemt_analysis

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

With no annotations, the description fully discloses behavioral traits: it explains the iterative BEMT convergence process, describes the theoretical foundation, mentions that errors are returned as formatted strings, and notes that ImportError is caught. This goes beyond minimal disclosure.

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 lengthy, with a detailed Note section that is more theoretical than practical for tool usage. While structured with Args/Returns/Raises sections, it could be trimmed without losing essential guidance.

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 (3 params, no annotations, output schema exists), the description covers return format, error handling, and some parameter hints. However, it lacks full specification of expected object keys and does not reference the output schema. It is adequate but not complete.

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%, so the description must compensate. It provides brief hints for each parameter (e.g., 'propeller_geometry: Propeller geometry (diameter_m, pitch_m, num_blades, etc.)'), but does not fully specify the expected structure or constraints. The examples help but are incomplete.

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's purpose: 'Analyze propeller performance using Blade Element Momentum Theory.' This is a specific verb+resource combination and distinguishes it from sibling tools like get_propeller_database, which retrieves data rather than performing analysis.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or what other tools might be more appropriate (e.g., for simpler performance estimates). There are no context signals about usage.

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