oracle_get_node

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

No annotations present, so description carries full behavioral disclosure burden. It only mentions 'best semantic match with full details' but does not disclose read-only nature, error handling (e.g., if no match found), or performance implications.

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?

Single sentence, concise and no redundancy. However, could be structured to include usage guidance or behavioral notes without extra length.

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?

Output schema exists (not shown) which likely explains return values. For a simple lookup tool, description covers core purpose but lacks error scenarios, usage context, and integration with sibling tools. Adequate but not complete.

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?

Only one parameter 'query' with no schema description (0% coverage). Description adds that the query is a 'description' for semantic search but lacks details on expected format, length, or examples. Does not compensate for schema gaps.

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?

Description clearly states 'Look up a node by description' with 'Finds the best semantic match with full details', specifying verb (look up), resource (node), and method (semantic match). Distinguishes from siblings like oracle_search_nodes (likely returns list) and oracle_list_nodes (lists all).

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?

Implies usage for finding a single node via semantic match, but does not explicitly state when to use this vs alternatives like oracle_search_nodes or oracle_list_nodes. No when-not or prerequisites provided.

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