cst_get_farfield

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

No annotations provided; description discloses the prerequisite and that it reads completed results. Does not mention error handling, performance, or that it is non-destructive. Acceptable but not exhaustive.

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 focused sentences: first states action and outputs, second states prerequisite. No wasted words, 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?

With no output schema, description lists returned items but not format. For a read tool with simple parameters, this is nearly complete. Could specify that results are numeric arrays or scalar, but the listed items imply scalar values.

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 covers both parameters with descriptions. Description adds meaning: frequency unit (GHz), monitor default naming convention, and condition that a monitor must exist. Adds value beyond schema.

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 'Get far-field radiation pattern results' with specific outputs (gain, directivity, efficiency, beam widths). Distinct from sibling tools like cst_get_gain or cst_get_radiation_pattern_3d by summarizing all far-field metrics.

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?

Explicit prerequisite: 'Requires a farfield monitor at the specified frequency.' Does not list when not to use or alternative tools, but the condition is helpful.

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