find-best-node

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

No annotations provided, so description must fully disclose behavior. It does not state whether this is a read-only operation, what data sources it consults, or how 'best' is determined. Lacks transparency about side effects or underlying logic.

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 without unnecessary words. Efficiently communicates core purpose, though could be slightly expanded for completeness without losing conciseness.

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?

No output schema and no description of return value. Does not explain what 'best node' means, what criteria are used, or how results are structured (e.g., node ID, score). Missing critical operational context for a selection tool.

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 0%, meaning description adds no parameter details beyond the schema. While the schema defines requiredResources and preferences, the description only vaguely references 'resources and preferences' without explaining how they influence the selection. Fails to compensate for low 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?

Description states 'Find the best node for VM placement based on resources and preferences', which clearly identifies the verb (find), resource (best node), and context (VM placement). It distinguishes from sibling tools like 'check-node-capacity' or 'discover-proxmox' by focusing on optimization rather than checking or discovery.

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 (e.g., 'check-node-capacity'). No prerequisites, exclusions, or context for selection. Simply describes functionality without usage direction.

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