provider_get_session

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 requires no description support. The description contributes the constraint that only the caller's own session is returned, but says nothing about behavior when the id belongs to another user or does not exist (error/404/403).

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 short lines: the purpose first, then the raw endpoint path, with no filler. The path line is somewhat redundant with the annotation title, but it aids mapping and does not bloat the definition.

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 tool with rich annotations, the essentials are present. With no output schema, however, the description could note what a session record contains (user, org, expiry, token) — without that, the agent cannot judge whether the response will answer its question.

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%, so the single 'id' parameter is documented structurally, which sets the baseline at 3. The description does not clarify whether the id is a session token, a numeric session id, or a URN — so it adds nothing beyond the schema.

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?

States a specific verb and resource ('Returns the specified session') plus a scope qualifier ('for current user'), which is more than a tautology. It does not, however, disambiguate against close siblings such as provider_get_current_session or provider_get_current_sessions, so an agent must still infer which one to pick.

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 guidance on when to use this versus provider_get_current_session, provider_get_current_sessions, or provider_post_1_0_0_sessions. The only cue is the implicit 'for current user' scoping, leaving selection entirely to inference.

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