Session Manage

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

No annotations are provided, so the description carries the burden. It discloses that the tool lists sessions and includes metadata fields, plus the server-global exclude_domains. It does not mention side effects, read-only nature, or any potential performance implications. Since it's a listing operation, the lack of explicit read-only disclosure is a minor gap, but the description is reasonably transparent about what it returns.

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 well-structured with a clear resource form, operation list, and canonical call shape. It is concise and front-loads the key information. The metadata field list is long but necessary for completeness. No redundant sentences.

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?

The description covers the list operation thoroughly, including metadata fields and the exclude_domains response. However, it does not explain the purpose of session_id or params in the context of listing, nor does it clarify if there are other operations beyond list. Given the output schema exists, return values are covered, but the parameter semantics gap remains.

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 description does not explain the parameters beyond the canonical call shape. It mentions 'op' and 'session_id' remain top-level, but does not explain what session_id is for or how params should be structured. The description adds some context about the call shape but fails to compensate for the lack of schema descriptions.

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 the tool lists every connected Godot editor with metadata, and the resource form is given. It is distinguishable from siblings like session_activate, which implies activation rather than listing. However, the title 'Session Manage' is broad and the description focuses on the list operation, so it doesn't fully clarify what other operations might exist.

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 implies usage for listing sessions and mentions a resource form preference, but it does not explicitly state when to use this tool versus alternatives like session_activate or editor_state. It also doesn't mention any prerequisites or context where listing is appropriate. The guidance is mostly implicit.

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