fmod_window_editorSelection

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

Lacking annotations, the description only states it returns an array of selected ManagedObjects. It does not disclose potential edge cases (empty array, invalid editor state), performance traits, or side effects. A simple read operation is implied but not explicit.

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 contains a duplicated sentence, which wastes space. It could be streamlined to a single sentence for better conciseness.

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 tool with no parameters or output schema, the description adequately explains what it returns and the context (last active editor). It lacks mention of return format (e.g., array of IDs or objects) but is mostly complete for a simple query.

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, and schema coverage is 100%. The description adds no parameter details, which is acceptable given the absence of parameters. Baseline 4 for zero-parameter tools.

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 clearly states it returns selected ManagedObjects from the last active editor, with an example (multitrack view). However, it repeats the same sentence twice, slightly reducing clarity, and does not differentiate from siblings like fmod_window_editorCurrent.

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 alternatives (e.g., fmod_window_editorCurrent, fmod_window_browserSelection). The description assumes the agent already knows when to query editor selection.

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