Create a slot antenna by generating a ground plane with a resonant slot and microstrip feed at a specified center frequency. Slot width auto-calculates if omitted.
Create a slot antenna in a ground plane. Generates the ground plane with a resonant slot and microstrip feed.
| Name | Required | Description | Default |
|---|---|---|---|
| frequency_ghz | Yes | Design center frequency in GHz | |
| slot_width_mm | No | Slot width in mm (auto-calculated if omitted) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes the creation action but does not disclose potential side effects (e.g., if it modifies existing geometry, requires certain coordinate systems, or whether it can be called multiple times). No annotations provided, so the description carries full burden.
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 sentences, efficient and free of extraneous information. Front-loaded with purpose.
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?
Lacks mention of return value or success indication. For a creation tool with no output schema, description should briefly state what the tool returns (e.g., object handle). Otherwise adequate.
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 description adds limited value. However, it mentions 'auto-calculated if omitted' for slot_width_mm, which supplements the schema definition.
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 creating a slot antenna in a ground plane, with generation of ground plane, slot, and microstrip feed. It uses specific verbs and resource names, distinguishing it from other antenna types like bowtie or dipole.
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?
No guidance on when to use this tool vs. alternatives (e.g., when a slot antenna is preferred over a patch antenna). No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.