fmod_project_buildStarted

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

No annotations provided. The description mentions 'callback' and 'property', but does not clarify behavior (e.g., whether reading returns current value, setting assigns a callback function or a value). Inconsistency between description and parameter semantics.

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 short, but lacks clarity. Conciseness is acceptable, but the structure does not effectively convey the tool's role.

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 output schema and the existence of related connect/disconnect tools, the description is incomplete. It does not explain the relationship to sibling tools or the full behavior (e.g., is it a property that fires callbacks?).

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?

The parameter description 'New value to assign. Omit to read the current value.' adds basic usage info, but does not explain what the value represents in the context of a build started callback. Schema coverage is 100%, so the description does not need to add much, but could be more specific.

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 is ambiguous: it says 'callback that will be fired' but the parameter schema implies it can be read or assigned a value. It does not clearly state whether this tool is for reading/writing a property or handling an event.

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?

No guidance on when to use this tool versus connecting/disconnecting callbacks (sibling tools). The description does not help an agent decide to use this over alternatives.

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