get_session_metadata

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

With no annotations, the description carries the transparency burden. It discloses that current_cpu_load is returned 'if available' and specifies units for song time/length, adding useful behavioral detail. It doesn't explicitly state that the operation is side-effect-free, but the 'get' prefix and read-only nature are strongly implied.

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 two focused sentences, front-loaded with the purpose and immediately listing return values. No filler or redundancy.

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?

An output schema exists, and the description also enumerates the return fields, making the tool fully comprehensible. With zero parameters and low complexity, no additional context is needed.

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, so the schema fully covers parameter requirements. The description need not add parameter semantics, and the baseline 4 applies.

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 uses a specific verb 'Get' and resource 'session metadata', and enumerates the exact fields returned (is_modified, current_song_time, song_length, current_cpu_load). This distinguishes it from sibling getters that focus on single aspects like get_song_time or get_application_cpu_usage.

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 usage context is clear: call this when you need composite session metadata. It doesn't explicitly name alternatives or exclusions, but the purpose is unambiguous and the composite nature makes it obvious when to use it over more specific getters.

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