cst_add_fixpoint_mesh

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

No annotations provided; description only mentions adding a fixed point but lacks details on side effects, permissions, what happens if coordinates already exist, or return values.

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 succinct sentences with no wasted words; purpose and benefit are 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?

Adequate for a simple creation tool, but lacks details on constraints (e.g., coordinate bounds, mesh requirements) and does not specify return behavior, which might be relevant.

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 100%; description adds no new meaning beyond 'at specific coordinates' and coordinate units (mm) which are already in schema. The 'name' parameter's description is minimal.

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?

Description clearly states the tool adds a fixed mesh point at coordinates, and distinguishes it from siblings like cst_add_mesh_refinement by specifying it ensures a node exactly at a location for precise field sampling.

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 usage for precise field sampling and accurate field probing, but does not explicitly state when to use versus alternatives like mesh refinement, nor when not to use.

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