set_keep_with_group

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

No annotations provided, so description must disclose behavior. It explains that value 'None' removes the element, indicating a destructive action. It does not mention permissions, prerequisites, or side effects. It is adequate but could be more thorough.

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 plus a short third. Front-loaded with the action. Every sentence adds value: action, value domain, typical use, and removal effect. No redundant words.

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 simple property setter with 4 required params and no output, the description covers purpose, value semantics, and typical use. It lacks details on path format and error conditions, but given the tool's simplicity, it is reasonably complete.

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 coverage is 0%, so description must add meaning. It explains the value enum (None, Before, After) and their typical effect. However, it does not explain the 'path' parameter format or the roles of 'tablix_name' and 'group_name'. This leaves ambiguity for correct 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?

Description clearly states it sets the KeepWithGroup property on a TablixMember for a named group. The verb 'Set', resource 'TablixMember>/<KeepWithGroup', and context 'member that wraps the named group' are specific. Distinguishes from sibling set_* tools by targeting a specific property.

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 a typical use case: column-header row's member with 'After' to glue it to data rows. This gives clear context for when to use. However, it does not explicitly state when not to use or mention alternatives like other properties.

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