compile_delphi_project

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

There are no annotations, so the text must carry the safety/behavioral burden. It discloses that the tool generates project structure, invokes dcc32/dcc64 or Free Pascal, defaults to a temp output directory, and emits a populated .dproj for fmx. It does not address overwrite behavior or compiler prerequisites, but the core side effects are clear.

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 front-loaded with the critical prohibition and tool purpose, then organized by Args with each parameter earning its place. Examples for components and events are compact but make an otherwise ambiguous JSON-string parameter concrete.

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 complex, unannotated, 8-parameter tool with 0% schema coverage, the description provides enough to select and invoke it correctly, including enum-like project types and conditional program_body usage. It does not explain what happens when compiler is null or when output_dir is omitted beyond the temp-directory note, but an output schema exists to cover return behavior.

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?

With 0% schema description coverage, the Args section is the only documentation for all 8 parameters. It explains project_type variants, gives JSON shapes and supported types for components/events, describes compiler choices and output_dir fallback, and ties program_body to console/fpc projects, far exceeding the bare schema.

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 first sentence names a precise action and resource: compile a Delphi project using DPR/PAS/DFM templates. It further claims to be the ONLY correct way to build Delphi applications, and the fmx note distinguishes it from build_dproj by generating a .dproj rather than building from one.

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 gives explicit direction: do NOT use MSBuild, shell commands, or other build systems, and it tells the agent to use project_type='fmx' when a mobile-ready or Android/iOS/macOS app is desired, with build_dproj as the follow-up. It does not explicitly compare against compile_pascal or run_pascal, but for Delphi project builds this tool is clearly positioned as the intended choice.

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