add_matrix

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

With no annotations, the description carries the full burden of disclosing side effects. It only says 'Add a matrix' and describes the data structure, but does not disclose that this modifies the report, requires an open session, or any other behavioral consequences. No safety profile is provided.

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 two sentences, front-loaded with the core action, and every word adds value. It is concise without being overly terse, though some necessary detail is missing.

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 tool with 10 parameters, no annotations, and no output schema, this description is insufficient. It explains only the data structure for rows/columns/values but omits how position, size, title, session, and page context work, leaving the agent without enough information to use the tool correctly.

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 description adds semantic meaning for rows, columns, and values, clarifying they are JSON arrays of {table,field,kind} and that values are measures. However, schema coverage is only 30%, and the description does not explain the other seven parameters (position, size, title, etc.), leaving most parameters under-documented.

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?

'Add a matrix' clearly states the action and resource, and the clarification about rows/columns/values as JSON arrays of {table,field,kind} distinguishes it from generic visual-add siblings like add_table_visual or add_chart. However, it doesn't explicitly mention 'visual' or 'to the report', so it's not fully specific.

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?

Usage is implied: you use this when you want to add a matrix with specified rows, columns, and values. But there is no explicit guidance on when to choose this over alternatives like add_table_visual or add_chart, nor any exclusions or prerequisites.

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