get_session_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists returned metadata fields but does not explicitly state that the operation is read-only, has no side effects, requires special permissions, or how errors are handled. 'Metadata' only weakly implies safe, non-mutating behavior.

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, front-loaded sentence that immediately states the resource and then lists specific metadata fields. There is no filler, repetition, or irrelevant information.

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 single-parameter metadata getter with no annotations and no output schema, the description partially suffices by listing expected content. However, it omits output shape, types/units, error behavior, and any prerequisites, which are more important given the absence of structured metadata.

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%, so the description must compensate by explaining session_id. It only says 'a session' without clarifying that session_id identifies the specific session whose metadata is returned. The parameter's meaning is left to the schema title and tool name.

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?

Description identifies the resource (a session) and enumerates concrete metadata fields (duration, channels, sampling rates, behaviour signals, licence, citation), which distinguishes it from siblings like get_signal_quality. It lacks an explicit verb, but the tool name supplies 'get' and the noun-phrase description is unambiguous.

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 use case is implied: call this tool when you need metadata about a session. However, it gives no explicit when/when-not guidance and does not contrast with related tools such as open_session, close_session, or get_signal_quality, leaving selection to inference.

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