get_motor_poles

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

No annotations provided, but description discloses consequence of wrong value ('filters tracking wrong frequencies'). Includes default and type info. Adds behavioral context beyond schema.

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?

Three concise sentences with front-loaded purpose, followed by context and warning. No extraneous text; earns every word.

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 parameterless read-only tool. Covers purpose, default, and criticality. Could mention pairing with setter, but not essential.

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?

No parameters (schema coverage 100%). Description adds value by stating default value and type '[UINT8, default: 14]' which is not in schema. Justified for 0-param tool.

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 it gets the number of magnetic poles. Specifies 'magnet count, not stator count', resolving common ambiguity. Distinguishes from sibling 'set_motor_poles' by being the getter.

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?

Explains importance for RPM filter accuracy and advises verifying on specific motors. Implicit usage context but lacks explicit when-not-to-use or alternatives. Adequate for a simple getter.

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