batch_create_footings_and_walls

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered. However, the description does not explain the destructive implications, what gets replaced or appended, how duplicates are handled, or what dry_run does, which are critical for a batch mutation with conflicting-sounding options.

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?

It is a single sentence with no wasted words, but it is under-specified for a complex tool rather than appropriately structured. The core action is front-loaded, but important qualifiers are absent.

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 destructive batch creation tool with 12 parameters and an output schema, the description is far too thin. It omits prerequisites, duplicate/replacement behavior, dry-run semantics, and how the project type mapping works, leaving major operational gaps.

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% across 12 parameters. The description only implicitly maps to the walls, pad_footings, and strip_footings arrays and does not explain level_name, dry_run, allow_duplicates, replace_existing, append_to_existing, offsets, or wall type mapping.

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 names a specific verb and resources ('Creates footings, walls and strip footings') and mentions the data source. It does not differentiate from the close sibling batch_create_structural_walls_and_foundations, leaving ambiguity about which batch tool to choose.

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?

There is no guidance on when to use this tool versus the similar batch structural tools, no prerequisites, and no mention of when not to use it. The agent must infer selection from the name alone.

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