set_tablix_size

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

No annotations provided, so description bears burden. It discloses that arguments are independently optional, both are RDL size strings, and returns an object with changed list, empty when no change. No mention of side effects but sufficient for a resize operation.

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 sentences, no wasted words. Front-loaded with action, then adds context about usage and return 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?

Covers purpose, parameters, return value, and usage context. Lacks details on permissions or error behavior, but adequate for a simple resize tool.

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 0% description coverage. Description explains that width and height are size parameters, optional, and use RDL strings. Does not detail name and path, but those are typical identifiers.

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 the action 'Resize a tablix' and the method 'writing <Height> and / or <Width> directly'. It distinguishes from sibling positioning tools by noting they only cover top/left, not size.

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?

Provides explicit guidance: 'Use after adding header / footer rows that change the body's natural height'. Compares to positioning tools, but does not explicitly state when not to use or alternative tools.

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