track_fx_get_count

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 correctly implies a safe read via 'Get' and discloses the return shape ('ret' field with the count), which is useful. However, it says nothing about error behavior for invalid track indices or how track_index relates to the project's track ordering.

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 short sentences, front-loaded with the action and followed by the return contract. No filler; the only minor cost is the labeled 'Returns:' block for a one-field result.

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 trivial read-only getter with no output schema, the description covers the essential outcome. It is not fully complete because the lone required parameter's semantics and the failure mode for a bad index are left unstated.

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 0% and the single parameter track_index has no type-level description. The description adds nothing about whether the index is 0-based, which track list it indexes into, or what a valid range is, so the sole parameter is effectively undocumented.

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 a specific verb and resource ('Get the number of FX plugins on a track'), which is clearly distinct from siblings like track_fx_get_list (list contents) and get_track_count (track count). It stops short of naming those siblings to route the agent explicitly.

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?

There is no guidance on when to use this versus track_fx_get_list, track_fx_get_num_params, or take_fx_get_count. The agent must infer usage purely from the tool name.

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