etabs_assign_area_load

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds the 'replace' parameter behavior but does not disclose side effects, error conditions, or the full effect of the operation beyond param details. Little new behavioral context is provided.

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 structured as a docstring with Args and Returns, which is clear and organized. It is concise, though the dir mapping could be more compact; nonetheless, every sentence is informative.

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 operation's simplicity and the presence of an output schema, the description covers the essential parameter semantics. It lacks prerequisites or post-conditions but is adequate for a straightforward assignment command.

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?

With 0% schema description coverage, the description fully explains each parameter: name, load_pattern, value (with units), dir (with value mapping), replace (semantics), and item_type (allowed values). This adds significant meaning beyond the schema's titles and types.

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 specific verb ('Assign') and resource ('uniform surface load to an area object'), clearly distinguishing it from sibling tools like etabs_assign_frame_load and etabs_assign_point_load. The details about parameters reinforce the purpose.

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 guidance on when to use this tool versus alternatives (e.g., frame or point load assignment). It does not mention prerequisites like requiring an existing area object or load pattern, nor does it exclude any use cases.

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