rsap_generate_mesh

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

With no annotations provided, the description carries the transparency burden. It discloses key behavioral traits: it only applies to shell models, is a no-op for bar/frame models, and meshing happens automatically on rsap_calculate(). This goes beyond the name and gives important operational context, though it doesn't mention potential errors or side effects.

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 two sentences with no wasted words. It front-loads the primary action, then provides a concise, valuable note about applicability. Every sentence earns its place.

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 simplicity (0 parameters, no output schema), the description is complete. It explains what the tool does, when it applies, and when it's a no-op, including the automatic mesh generation behavior. No critical information is missing for an agent to decide whether and how to invoke it.

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?

The tool has zero parameters, so the baseline is 4. The description doesn't add parameter-level details, but none are needed. The contextual note about model types compensates for the lack of parameters by clarifying when the tool is meaningful.

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 the tool's function with a specific verb and resource: 'Generate the finite-element mesh.' It also distinguishes from siblings by clarifying scope—only surface/panel (shell) models, and explicitly notes it is a no-op for bar/frame models, which differentiates it from other rsap_ tools.

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 clear context on when the tool matters (shell models) and when it's unnecessary (bar/frame models), even noting that Robot generates mesh automatically via rsap_calculate(). It stops short of explicitly stating 'use this instead of rsap_calculate' or naming alternatives, but the applicability guidance is strong.

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