get_track_count

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

The annotation declares readOnlyHint=true, and the description is consistent with that by using 'Get the total number'—a safe read operation. It adds useful behavioral scope beyond the annotation by clarifying that the master track is not counted, which is a meaningful edge-case disclosure.

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 a single well-structured sentence that front-loads the action ('Get the total number of tracks') and immediately specifies the scope and exclusion. There is no redundant or filler content.

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 zero-parameter, read-only counting tool with no output schema, the description is complete: an agent knows exactly what is counted, what is excluded, and that the result is a track count. No additional context is needed to invoke this tool correctly.

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 tool has zero parameters and the schema is an empty object, so there is no parameter semantics burden on the description. This matches the baseline of 4 for parameterless 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 states a specific verb and resource: it gets the total number of tracks in the current REAPER project. It also disambiguates the scope by explicitly excluding the master track, which differentiates it from related track-querying siblings like get_all_tracks and get_master_track.

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?

The description gives clear context by specifying 'current REAPER project' and 'excluding master track', so an agent can infer when to use this read-only counting tool. It does not explicitly name alternative tools or provide when-not-to-use conditions, but for a zero-parameter query this level of context is sufficient.

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