session_set_name

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

No annotations are provided, so the description carries full burden. It states the tool sets a name, implying a mutation, but does not disclose behavioral traits such as whether this requires specific permissions, if changes are reversible, potential side effects, or error conditions. The description is minimal and lacks crucial operational context for a mutation tool.

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 appropriately sized and front-loaded with the main purpose in the first sentence, followed by parameter details. It avoids unnecessary fluff, but the parameter explanations could be slightly more integrated into the flow rather than listed separately, though this is minor.

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?

Given that annotations are absent and there is an output schema (which reduces the need to describe return values), the description is partially complete. It covers the basic purpose and parameters but lacks behavioral transparency and detailed usage guidelines, which are important for a mutation tool with no annotation support, leaving gaps in overall context.

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. It adds meaningful semantics: 'name' is described as 'The new session name' and 'session_id' as 'Target session ID. Omit for the active session.', which clarifies purpose and default behavior beyond the bare schema. This effectively covers both parameters, though it could provide more detail on format or constraints.

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 action ('Set the name') and target resource ('an iTerm2 session'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like session_set_variable, which might also modify session properties, leaving room for slight ambiguity in sibling distinction.

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 provides implied context by noting that session_id can be omitted for the active session, suggesting usage when targeting specific or default sessions. However, it lacks explicit guidance on when to use this tool versus alternatives like session_set_variable or other session-related tools, and does not mention any exclusions or prerequisites.

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