set_repeat_on_new_page

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

No annotations are provided, so the description must disclose behavioral traits. It mentions that setting repeat=False removes the element and specifies the return object, but omits side effects, permission requirements, error conditions, or the need for an editing transaction.

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 with no unnecessary words. Directly conveys the action, common use, and return value. Front-loads the key information.

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 4 required parameters, no annotations, no output schema, and a complex domain (report tablix member updates), the description is under-specified. Lacks context about the 'path' parameter, the editing transaction requirement, and how this fits with sibling tools like start_editing_transaction.

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 parameters with 0% description coverage. The tool description does not explain any parameter meanings (e.g., 'path', 'tablix_name', 'group_name', 'repeat'). The return object hints at 'tablix', 'group', and 'repeat', but this is insufficient for correct parameter usage.

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 verb 'Set' and the resource 'RepeatOnNewPage' property on a TablixMember, with a specific use case of repeating group header rows. It distinguishes from sibling tools by specifying the context of group header repetition.

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 the most common use case but does not explicitly guide when to use this tool versus alternatives like other set_ operations. No exclusions or prerequisites are mentioned.

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