convert_to_matrix

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

No annotations provided, so description carries full burden. Discloses the transformation action, pre-condition checking, and refusal behavior. Missing details on error messages, idempotency, and permission requirements, but core behavioral traits are covered.

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?

Front-loaded with action, then pre-conditions and use-case. Sentences are information-dense without fluff. Could be slightly trimmed but remains efficient.

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?

Despite complexity, no output schema exists and description does not mention return value, error handling, or side effects beyond the stated transformation. Leaves agent guessing about success/failure signals.

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 4 required params with 0% coverage. Description only implies row_group and column_group are the named groups but adds no format, constraints, or details about path and tablix_name. Fails to compensate for missing schema descriptions.

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?

Clearly states the verb 'convert', resource 'tablix', and outcome 'into a matrix by dropping residual Details row group'. Distinguishes from siblings by referencing the workflow sequence and pairing with set_tablix_corner.

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?

Explicitly lists pre-conditions (row_group/column_group existence, Details group presence), states refusal on second call, and provides the recommended workflow order. Clearly tells when to use and when not.

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