civil3d_profile

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

No annotations are provided, so the description must disclose behavioral traits. It lists actions but does not specify side effects (e.g., creation modifies drawing, deletion is destructive), required permissions, or state changes. This is insufficient for a tool with both read and write operations.

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?

The description is a single sentence that front-loads the main purpose and lists actions concisely. Every part earns its place with no redundant or wasted 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?

Given the tool's complexity (multiple actions, 7 parameters) and no output schema, the description lacks details on return values or side effects. It does not explain what each action produces or changes, making it incomplete for a complex tool.

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 100%, so the baseline is 3. The description adds value by mapping actions to parameters (e.g., list by alignment implies use of alignmentName), but it does not fully detail which parameters are required for each action, leaving some ambiguity.

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 clearly states it manages Civil 3D profiles (vertical geometry) and enumerates specific actions (list, get, get_elevation, create_from_surface, create_layout, delete). This distinguishes it from sibling tools like civil3d_alignment (horizontal) and civil3d_surface.

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 provides context by listing actions with parenthetical notes on required parameters (e.g., list by alignment, get by alignment + name). However, it does not explicitly state when to use this tool versus alternatives or include exclusions.

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