set_row_height

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

No annotations provided, so the description must carry the full burden of behavioral disclosure. It only states the action and parameter details without mentioning side effects, prerequisites (e.g., table must exist), or the nature of modification (in-place, irreversible).

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 concise, with a clear sentence and structured bullet list for rule options. No redundant information; every sentence serves a purpose.

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's simplicity (4 params with a rule enum) and the existence of an output schema (indicated), the description covers parameter semantics and return value. However, it lacks mention of valid ranges for height_cm or row indices and does not state that the table must exist, which are minor gaps.

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 clearly explains each parameter's purpose (table_index, row_index, height_cm) and provides explicit details for the rule parameter, including allowed values and their meanings, which is essential.

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 'Set the height of a specific row in a table' with a specific verb and resource, distinguishing it from sibling tools like set_column_width or set_cell_text.

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?

No explicit guidance on when to use this tool versus alternatives like set_table_cell_shading or edit_table_cell. The description only explains the operation without context for when it's appropriate.

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