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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds the meaningful detail that the metadata is 'privacy-filtered,' which is not captured by annotations. This goes beyond the structured fields, though it doesn't discuss error cases or the return format.

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?

A single, front-loaded sentence with the verb 'Read' at the start. No filler or redundancy. It is appropriately concise for a simple read operation.

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 with annotations covering safety, the description is mostly complete. The privacy-filtered note adds useful context. However, it doesn't mention what the output contains or how the session is identified beyond the parameter. Given the lack of an output schema, a little more detail on the return value would be helpful, but it is not critical.

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 does not explain what projectId is or how it maps to a session. The only hint is the tool name itself. The pattern and maxLength in the schema are technical constraints, not semantic guidance. The description fails to add any meaning to the parameter.

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 a read action on a 'hosted open project session' with privacy-filtered metadata. It names the resource and the operation, making it distinguishable from listing tools like list_project_sessions. However, it doesn't explicitly contrast with other read tools like get_project_status or project_read, so it's not a 5.

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?

No guidance is given about when to use this tool versus alternatives. The description never mentions conditions such as 'use this to open a specific session' or contrasts with list_project_sessions. The agent must infer usage from the tool name and schema alone.

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