fmod_project_buildEnded_disconnect

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

No annotations provided, so the description carries full burden. It discloses that failing to disconnect can cause signals to accumulate and lead to unexpected behavior, which is a behavioral warning. However, it does not describe the exact effects of disconnection (e.g., idempotency, state changes).

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?

Two clear sentences plus a reference. Efficient and front-loaded, though the first sentence could be slightly more direct. No wasted words.

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 simple parameterless tool, the description covers purpose and consequence of not using. It does not explain how to obtain the connectFunction, but that is likely documented in the connect tool's description. Given the simplicity, it is adequately complete.

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?

No parameters exist, so schema coverage is 100%. The description adds no parameter information, but with zero parameters, the baseline is 4. Nothing needed beyond what the schema provides.

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 states it disconnects a 'connectFunction' when no longer needed, and the bracketed '[method · project.buildEnded.disconnect]' clarifies it relates to the buildEnded event. It distinguishes from its sibling connect tool, but could be more explicit about what the connectFunction is.

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?

It advises disconnecting 'once it is no longer needed' and warns about not doing so, but lacks explicit when-to-use versus alternatives (e.g., other disconnect tools). The guidance is general and implied.

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