rhino_get_document_text

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

With no annotations provided, the description carries the full burden, but it only says 'Retrieve' without disclosing behavior for missing keys, empty values, or whether multiple keys can be accessed. The operation is clearly a read, so no destructive behavior is implied, but return edge cases are not covered.

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 short and the main sentence is front-loaded and information-dense. The 'Args:' section is largely redundant with the schema, but it does not bloat the description significantly.

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?

For a one-parameter getter, the description identifies the resource and input, and an output schema is present to describe the return. However, it omits missing-key behavior and does not clarify relationship to sibling user-text tools, leaving some context for the agent to infer.

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%, so the description must compensate. It merely restates 'key: Key name,' which adds little beyond the property name itself. It provides no guidance on valid key formats, how to discover document-level keys, or what happens for absent keys.

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 uses a specific verb ('Retrieve') plus a clear resource ('document-level user text value') and mechanism ('by key'). The term 'document-level' distinguishes it from sibling tools like rhino_get_user_text, which operate at the object level.

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 implies this tool is for reading document-level custom text values, but it does not explicitly state when to prefer it over rhino_get_user_text or when not to use it. No alternative or exclusion is mentioned.

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