etabs_set_stories

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

The description only says 'define', which implies a mutation, but it does not disclose whether existing stories are overwritten, if the model must be unlocked, or if the arrays must have matching lengths. No annotations are provided, so the description carries the full burden and fails to convey these behavioral aspects.

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 a single, concise sentence that front-loads the action verb and clearly states the object. It avoids unnecessary detail and is easy to parse.

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 tool has 5 parameters (including optional ones) and an output schema, the description is insufficient. It omits key context about optional parameters, their interactions, and any return values or side effects. This makes the tool difficult to use correctly without additional documentation.

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 schema lists 5 parameters, but the description only clarifies 'names' and 'heights' (via 'niveles' and 'altura'). It does not explain the purpose or effect of `similar_to`, `base_elevation`, or `master_stories`, leaving 3 out of 5 parameters undocumented. Since schema description coverage is 0%, the description must compensate, but it does not.

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 verb 'Define' clearly indicates a setter action for story levels, and the resource 'stories' is specific. The phrase 'de abajo hacia arriba' (from bottom to top) adds ordering context, distinguishing it from the sibling tool `etabs_stories` which likely queries or retrieves stories.

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 like `etabs_stories` (which may be a getter) or other story-related tools. There is no mention of prerequisites, such as having an open model or being in a specific unit system.

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