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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds a small behavioral detail by saying the list uses 'privacy-filtered project metadata,' but it does not disclose output shape, pagination, or what privacy filtering actually affects.

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 short sentence with no filler or redundant phrases, and the main action is front-loaded. The wording is somewhat unclear, but it earns conciseness credit by avoiding unnecessary detail.

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, read-only, idempotent tool, annotations and schema cover safety and the required input. However, there is no output schema, and the description does not clarify what a project session is, what the returned list contains, or how 'hosted' and 'privacy-filtered' shape the results.

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 the meaning of projectId beyond what the parameter name implies. The name and pattern make it somewhat self-explanatory, but the description fails to compensate for the missing schema-level documentation.

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 uses a specific verb, 'Read,' and names the resource, 'list project sessions,' so an agent can infer it returns a collection of sessions. However, it does not explicitly differentiate itself from related siblings like open_project_session or list_project_versions, and the phrasing 'hosted list project sessions' is grammatically awkward.

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 explicit guidance about when to use this tool instead of alternatives, and no conditions or exclusions are stated. The phrase 'privacy-filtered project metadata' hints at a scoping constraint but does not give an agent a decision rule for selecting this tool.

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