hwp_table_formula_avg

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

No annotations provided. Description indicates an action but does not disclose side effects (e.g., inserting a formula field, overwriting cell content, or requiring specific selection state). Minimal behavioral context.

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?

Two short sentences, front-loaded with purpose. No unnecessary words; every sentence adds value.

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?

Tool has one parameter (table_index), no output schema, and no annotations. Description is minimal and does not explain what 'average' computes (column/row/custom range), nor the effect on the document. Lacks detail for full understanding.

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 has 100% coverage with parameter description 'table_index' (표 인덱스). The description does not add additional meaning beyond what is in the schema, so baseline 3 is appropriate.

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?

Description clearly states it calculates average in a table using an automatic function at the current cell position. It is specific about the action and resource, but lacks detail on the scope (e.g., row vs column average). Distinguishes from sibling 'hwp_table_formula_sum' by operation name.

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 guidance on when to use this tool versus alternatives like hwp_table_formula_sum or other table operations. No explicit context or exclusion criteria.

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