get_collaboration

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, but the description adds valuable behavioral context beyond them: link collaborators may appear only in presence, invitedMembers is not a complete participant list, online connections are grouped by account, and unavailable presence is reported as unknown.

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 three sentences with the core read behavior front-loaded, followed by focused caveats about presence and invited-member completeness. Every sentence adds useful information without repetition.

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 one-parameter read tool with annotations covering safety, the description gives useful output and completeness semantics. It still omits projectId scoping and there is no output schema, but the core behavioral picture is largely complete.

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 only parameter, projectId, is never mentioned in the description. The parameter name is self-explanatory and the schema supplies a pattern, but the description does not compensate for the missing schema documentation or explain scoping semantics.

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 states a specific verb and resource: it reads explicitly invited members and current online users separately. It also clarifies the two datasets and their caveats, though it does not name sibling tools or explicitly differentiate itself from tools like get_session_status.

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 opening 'Read...' implies the tool is for inspecting collaboration and presence, but there is no explicit when-to-use guidance, no exclusions, and no named alternative such as get_session_status. Usage is therefore only implied.

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