rhino_get_rhinoscript_docs

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

Annotations already declare readOnlyHint=true, and the description adds behavioral details about what the tool returns: 'full signatures, parameter descriptions, return values, and optional code examples.' This supplements the annotation well, though it omits potential failure modes or rate limits.

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 extremely concise with three short sentences, each serving a distinct purpose: defining the action, giving a critical usage rule, and listing return contents. No unnecessary words or 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?

The description is adequate for a documentation-lookup tool with an output schema, mentioning return types and a critical prerequisite. However, it does not mention the configurable parameters (max_functions, include_examples) despite their existence, leaving a gap for the agent to know customization options.

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%, meaning the description must compensate for missing parameter details. The tool description only mentions 'topic' implicitly but does not explain the meaning or usage of any parameters (topic, max_functions, include_examples). The existing schema descriptions are not considered as per coverage metric, so no additional value is provided.

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 retrieves 'comprehensive RhinoScript documentation for a topic,' with a specific verb and resource. It distinguishes from siblings like rhino_search_rhinoscript_functions by focusing on topic-based lookup and explicitly requiring usage before rhino_execute_python, making its role unique.

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 explicit guidance by stating 'You MUST call this tool before using rhino_execute_python,' which is a strong usage rule. However, it does not mention alternatives or when not to use it, leaving some context unaddressed.

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