cad_suppress

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

Discloses that the feature remains in the tree, but lacks details on side effects (e.g., impact on downstream features) and permissions, especially with no annotations.

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?

Single sentence with no redundant information, appropriately front-loaded.

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 tool with 5 required parameters, no output schema, and no annotations, the description omits crucial context like reversibility, prerequisites, and behavior when already suppressed.

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?

Only clarifies 'featureId' and 'suppressed' from the five required parameters; documentId, workspaceId, elementId are unexplained despite 0% schema coverage.

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?

Clearly states the action (suppress/unsuppress) on a specific resource (feature by featureId) and the effect (leaves it in the tree), distinguishing from deletion.

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?

Implies toggling visibility without removal, but no explicit when-to-use or comparison with sibling tools like cad_delete_feature or cad_edit_feature.

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