Add Table To Group

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

Annotations already declare the operation is mutating but non-destructive and non-idempotent (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the safety profile is covered. The description adds only that the table must be an existing standalone table already in the map, a useful prerequisite, but omits failure modes, permission needs, and what the mutation changes.

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?

A single front-loaded sentence with no filler. It is efficient, though arguably too terse given the schema carries no parameter documentation.

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?

An output schema exists so return values need no explanation, but for a 4-parameter mutating tool with 0% schema coverage the description is far too thin. It should at least clarify the roles of aprx_path and map_name and any prerequisites for the operation to succeed.

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 description coverage is 0% for all 4 required parameters, so the description must compensate. It loosely maps to table_name and group_layer_name ('existing standalone table', 'target group layer') but says nothing about aprx_path or map_name, leaving half the parameters undocumented.

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?

States a specific verb (add) and resource (an existing standalone table) plus the target (a group layer), which is clear enough to distinguish from the sibling add_layer_to_group. However, it does not explicitly name or contrast with that sibling, so an agent must infer the layer/table distinction.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It does not tell the agent how this differs from add_table_from_path or add_layer_to_group, leaving selection to inference.

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