Delphi Build MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: default behavior (creates separate platform-specific files), file naming patterns (e.g., delphi_config_win32.toml), and input requirements (multiple logs). However, it lacks details on error handling, output format beyond file names, or performance implications, leaving gaps for a tool with 5 parameters.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by specific behavioral details and usage guidelines. Every sentence adds value without redundancy, making it efficient for an agent to parse and understand the tool's role quickly.

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 (5 parameters, no annotations, no output schema), the description is reasonably complete. It covers purpose, usage context, and key behaviors, but lacks details on output structure or error handling. For a config generation tool with multiple parameters, it provides sufficient context for basic use, though not exhaustive.

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%, providing detailed parameter documentation. The description adds minimal value beyond the schema, mentioning platform-specific file naming and the multi-log context, which are implied by the tool's purpose but not parameter-specific. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't significantly enhance parameter understanding.

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 tool's purpose: 'Generate delphi_config.toml file from multiple IDE build logs for different configurations and platforms.' It specifies the verb ('generate'), resource ('delphi_config.toml file'), and source ('multiple IDE build logs'), distinguishing it from sibling tools like 'generate_config_from_build_log' (singular) and 'extend_config_from_build_log' (extending existing config).

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 explicitly states when to use this tool: 'Use this when you have build logs from multiple configurations (Debug/Release) and/or platforms (Win32/Win64/Linux64).' This provides clear context for usage versus alternatives, helping the agent choose this tool over siblings like 'generate_config_from_build_log' for single logs.

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