lc_get_lookup

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

Without annotations, the description carries the full burden for behavioral disclosure. 'Fetch' implies a non-destructive read operation, but no details are given about idempotency, error states, or authorization requirements. The description is too terse to compensate for the lack of 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 a single sentence with no wasted words. While concise, the brevity results in omitted critical information. It earns a 4 for structure but is undermined by lack of content.

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 tool is simple (2 required params, no output schema), but the description fails to provide essential context about parameter usage and return expectations. An agent cannot reliably use this tool without additional information.

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?

The input schema has two required parameters (oid, name) with 0% description coverage in the schema. The description does not explain what these parameters represent or how to use them, leaving the agent with only parameter names to infer meaning.

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 'Fetch one lookup Hive record' clearly states the action (fetch) and the resource (lookup Hive record). It distinguishes from siblings like lc_list_lookups (lists lookups) and lc_get_hive_record (general Hive record fetch). However, it could be more explicit about what makes 'lookup' records distinct.

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?

No guidance on when to use this tool versus alternatives like lc_list_lookups or lc_get_hive_record. The description does not mention prerequisites or context for using 'lookup' specifically.

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