lookup_function

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

Discloses fuzzy matching, 'did_you_mean' list, and full return record (signature, parameters, etc.), fully informing the agent of behavior without 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?

Concise with clear bullet-like listing of return fields; every sentence adds value without redundancy.

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?

Complete for a single-parameter tool without output schema; covers return content, fallback, and examples adequately.

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?

Provides concrete examples like 'llListen' and 'llReplaceSubString,' adding value beyond the schema, though schema coverage is 0%.

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 'Look up an LSL function by name,' distinguishing it from sibling 'search_functions' by emphasizing exact lookup and fuzzy fallback.

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?

Indicates use for exact names with fallback and 'did_you_mean' for non-matches, but doesn't explicitly contrast with 'search_functions' or specify when not to use.

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