kremis_intersect

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

With no annotations, the description must carry the transparency burden. It only states the basic operation without disclosing what 'connections' means (e.g., edges, neighbors), output format, side effects, or error states. Minimal behavioral insight.

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, front-loaded sentence of 8 words. No extraneous information; all words are meaningful and earn their place.

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?

Despite good schema coverage, the description lacks context about return format, what a 'common connection' resolves to, and how it integrates with sibling tools. It is insufficient for an agent to fully understand usage in the graph system.

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 coverage is 100% with a description for the 'nodes' parameter. The tool description adds 'common connections', clarifying the operation intent, but does not provide additional parameter syntax or constraints beyond the schema. Baseline 3 is appropriate.

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 'Find common connections between multiple nodes' uses a specific verb ('Find') and resource ('common connections'), clearly distinguishing it from sibling tools like kremis_path (path traversal) and kremis_lookup (single node retrieval).

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 kremis_path or kremis_traverse. No prerequisites, exclusions, or context for when 'common connections' is the appropriate query.

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