etabs_define_rebar

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

Annotations indicate the tool is not read-only, not destructive, not idempotent, and not open-world. The description adds minimal behavioral context beyond stating it returns a confirmation. It does not disclose potential side effects like creating a new database entry or validating input, which would be helpful given the lack of annotation detail.

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 concise: a single sentence for purpose followed by clear parameter definitions and return value. Every sentence serves a purpose with no redundancy.

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?

For a definition tool with 3 required parameters and an output schema, the description covers basic semantics but lacks context about preconditions (e.g., model must be open), error conditions (e.g., duplicate name), or the exact structure of the confirmation response. The output schema exists but is not provided, so the agent cannot rely on it for completeness.

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 compensates by explaining each parameter: name with examples ('#4', '#8'), area as 'cross-sectional area in current units', and diameter similarly. This adds meaning beyond the raw schema 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 'Define a rebar size' uses a specific verb and resource, clearly indicating the tool's purpose. It effectively distinguishes from sibling tools like define_area_section or define_frame_section, which define different structural elements.

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 such as other define_* tools. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision support.

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