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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so the safety profile is fully covered. The only added phrase, 'privacy-filtered project metadata,' is too vague to be actionable – it doesn't say what is filtered out, what a session contains, or whether results are paginated.

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?

It is a single short sentence with no padding, which is positive, but the sentence itself is ungrammatical ('Read hosted list project sessions'), so brevity comes at the cost of a clear, front-loaded statement of purpose.

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 single-parameter list tool this is thin: the description never defines what a 'project session' is, how it relates to open_project_session, or what the result set looks like. With no output schema, the description should carry more of the return-shape burden than it does.

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 coverage is 100% and there is only one parameter, so the schema already documents projectId thoroughly (including the 'do not use a local path' warning). The description adds nothing beyond it, making the baseline 3 correct.

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 resource is identifiable (project sessions) and the verb is list, but the phrasing is garbled – 'Read hosted list project sessions' – mixing 'read' and 'list'. It does not distinguish itself from siblings like list_linked_projects, list_project_versions, or open_project_session, so an agent must guess which session-related tool to call.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Nothing tells the agent why to pick this over open_project_session or the other list_* tools.

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