get_api_for-ffi

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, pagination, error handling, authorization needs). The agent cannot infer safety or side effects.

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?

Extremely brief but lacking essential information. Conciseness should not come at the cost of clarity; a single phrase is insufficient for an agent to understand the tool's capabilities.

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?

Given the absence of annotations and output schema, the description should compensate. It does not explain the output format, result interpretation, or any constraints (e.g., whether it returns a list or single result, required dependencies).

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 descriptions for 'class' and 'method' are clear ('The class name to search for.' and 'The method name to search for.'). The tool description adds no additional semantic value beyond the schema. Baseline score of 3 is appropriate due to high schema coverage.

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 'Node.js API: FFI' only identifies the module but lacks a verb or clear action. It does not specify what the tool does (e.g., retrieve documentation, list APIs, search). The sibling tools share a similar naming pattern, so the description does not distinguish behavior.

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. The sibling tools differ by module name, but the description provides no context for selection, such as prerequisites or conditions.

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