get_session_presence_tool

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

No annotations are present, so the description carries the behavioral burden. It discloses what data is reported and implies a read-only presence query, but it does not explicitly state that it makes no modifications, whether it requires an active session, or how it behaves when collaborators are absent.

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 compact sentence with a well-structured colon-delimited list. It front-loads the core question and contains no filler or redundant wording.

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 simple read-style tool with an output schema, the description covers the main response dimensions adequately. However, with no annotations and no usage guidance, it leaves some behavioral and selection context implicit, making it minimally complete rather than fully self-sufficient.

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 project_path or its expected format. The parameter name and title are moderately self-explanatory, but the description adds no direct semantic value beyond placing the tool in the Sharecut Studio session domain.

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 identifies the tool as a presence query for the Sharecut Studio session and lists concrete attributes (display names, cursor, selection, viewport, transport, follow relationships). It avoids tautology and is conceptually distinct from nearby session tools, though it does not explicitly name its closest sibling.

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?

There is no guidance about when to use this tool versus alternatives such as get_session_state_tool or other session-control tools. The agent must infer that this is the read-only presences snapshot from the name and description alone.

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