fmod_project_build

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

No annotations provided, so description carries full burden. It states the operation builds banks, returns true/false. However, it does not disclose whether the operation is synchronous or async, side effects (e.g., overwriting files), or error behavior. Adequate but could be more detailed.

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 with return info and reference tag. Every part is informative and non-redundant. Front-loaded with the core action.

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 no parameters and no output schema, description is quite complete: explains scope (all banks, all platforms from preferences) and return value. Minor missing detail: blocking vs async, but overall sufficient for a simple 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?

Zero parameters, so no param info needed. Baseline is 4 for 0 params. Description adds no extra parameter info as there are none.

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 clearly states it builds all banks to all platforms from preferences. The verb 'Builds' and resource 'banks' are specific. It distinguishes from sibling tools like event hooks (buildStarted/buildEnded) and other project actions (create, save).

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?

Implies usage when banks need to be built, but no explicit guidance on prerequisites (e.g., project must be saved) or when to use this vs listening to build events. No exclusions or alternatives mentioned.

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