ILP Drone Delivery MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'optimization' but doesn't describe what that entails (e.g., minimizing distance, time, cost), whether it's a read-only planning operation or executes deliveries, what permissions are needed, or any rate limits. For a complex multi-drone routing tool with zero annotation coverage, this is inadequate.

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, efficient sentence that front-loads the core purpose. Every word earns its place—'plan routes', 'multiple deliveries', 'simultaneously', 'multi-drone optimization'—with zero waste or redundancy. It's appropriately sized for the tool's complexity.

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 tool's complexity (multi-drone optimization), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., routes, assignments, cost estimates), behavioral traits, or usage constraints. For a planning tool with significant operational implications, more context is needed.

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 description coverage is 100%, so the schema already documents the single 'deliveries' parameter and its nested structure. The description adds no additional parameter semantics beyond what's in the schema (e.g., explaining what 'capacity', 'heating', or 'cooling' mean in context). Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('plan routes') and resource ('multiple deliveries'), and specifies the optimization approach ('multi-drone optimization'). However, it doesn't explicitly differentiate from its sibling 'plan_delivery' tool, which appears to be a single-delivery version. The purpose is specific but lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'plan_delivery' or other drone-related tools. It mentions 'multi-drive optimization' but doesn't specify prerequisites, constraints, or when this approach is preferred over single-drone planning. No explicit when/when-not statements are present.

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