Get Exploratory Session

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

readOnlyHint=true already establishes the safe-read profile, so the description's job is only to add context. It adds the returned-field inventory, which is useful given there is no output schema, but says nothing about whether a missing/unknown sessionId errors, what permissions are required, or how attachments/findings are shaped.

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?

Two sentences, zero filler. The purpose and returned fields come first and the ID-format note follows as a second, clearly bounded sentence.

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?

With no output schema, the field enumeration meaningfully tells the agent what it will receive, and the readOnly annotation covers the safety dimension. It is missing error/not-found behavior and permission requirements, but for a two-parameter read tool it is close to 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 100% and the schema already documents sessionId as "Internal _id or counter-style ID"; the description largely restates this while adding a concrete example ("SES-12"). The projectId parameter receives no additional scoping or format detail, so this is close to the baseline of 3 with a marginal edge from the example.

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?

Specific verb (Get) plus resource (one exploratory session) with an enumeration of the fields returned, which makes the tool's output easy to anticipate. It implicitly separates itself from list_sessions/create_session/update_session via "one", but never names a sibling or states the boundary explicitly, so it stops short of 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 when-to-use guidance at all: nothing tells the agent to reach for this instead of list_sessions when scanning, or update_session when mutating. The only implied usage comes from the word "one" and the field list; no prerequisites, no exclusions, no alternatives are stated.

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