configure_bd_cell

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

With no annotations, the description carries the full burden: it discloses that this is a mutation of an existing cell and reveals the underlying set_property -dict mechanism, which is genuinely useful. It does not say whether an open block design/session is required, whether unknown CONFIG.* keys error out or are silently ignored, or whether the change is reversible — significant omissions for a mutating tool with zero annotation coverage.

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 tightly packed sentences with the purpose front-loaded and the usage condition following immediately; nothing is filler. The PS7 example earns its space by showing the config dict shape, though it slightly muddies routing by invoking a scenario that has its own sibling tool.

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 2-parameter mutation tool with a nested object parameter, no annotations, no output schema and only 50% schema coverage, the description covers purpose, timing and value format but leaves prerequisites (open design? active session?) and failure semantics unexplained. Adequate to start a call, not complete enough to call confidently.

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 only 50% (cell_name has no description), but the description compensates: it clarifies that config is a dict of CONFIG.* properties and gives a concrete key/value example showing the expected string format. cell_name is implicitly defined by 'on an existing block-design cell', though its naming/format convention is never spelled out.

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 and resource ('Set CONFIG.* properties on an existing block-design cell') and even names the underlying Tcl command (set_property -dict), so the operation is unambiguous. It never names a sibling to differentiate from, however, and its PS7 example overlaps with the dedicated apply_ps7_preset tool without acknowledging the 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?

Gives clear context: 'Use for settings that must be applied after creation or in a separate step', which tells an agent when this is the right entry point versus passing properties at creation time. It stops short of exclusions or alternatives — notably it does not mention apply_ps7_preset, which is the sibling an agent would most plausibly confuse with this one.

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