rhino_search_rhinoscript_functions

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

Discloses that it returns matching functions sorted by relevance, which aligns with readOnlyHint annotation. No contradictions; provides behavioral context beyond annotations.

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 concise, front-loaded with purpose, and includes useful example queries. Every sentence adds value without fluff.

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 simple search functionality, annotations, and output schema existence, the description is complete with usage guidance and examples. The limit parameter omission is a minor gap but not critical for basic use.

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 0% per given context, and the description only explains the 'query' parameter via examples but omits any reference to the 'limit' parameter. The description adds limited value for parameter understanding.

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 searches RhinoScript functions by keyword or description, and distinguishes it from sibling tools by specifying its use case for finding correct function names before writing code.

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?

Explicitly advises to use this tool before writing any RhinoScript Python code, and provides example queries. Lacks explicit when-not-to-use or alternatives, but context implies it's for discovery.

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