Delphi Build MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains what gets returned (compilation errors only) and mentions automatic reading of configuration files, which adds useful context. However, it doesn't cover important aspects like error handling, performance characteristics, permission requirements, or what happens when compilation succeeds.

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 efficiently structured in two sentences that each serve distinct purposes: the first explains the core functionality and automation, the second specifies the output filtering. There's no wasted language or redundancy.

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?

For a compilation tool with 6 parameters and no output schema, the description provides basic functionality and output filtering but lacks completeness. It doesn't explain what happens on successful compilation, error formats, or how results are structured. With no annotations and no output schema, more behavioral context would be helpful.

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 all parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 specific action ('Compile a Delphi project'), identifies the resource ('.dpr or .dproj file'), and specifies the output ('returns only compilation errors, filtering out warnings and hints'). It distinguishes itself from sibling tools by focusing on compilation rather than configuration generation from build logs.

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 or under what conditions it should be invoked. While it mentions automatic reading of build configuration and library paths, it doesn't specify prerequisites, limitations, or comparison with sibling tools that work with build logs.

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