Get one JWT session by id

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

The description uses 'Read' which is consistent with annotations (readOnlyHint, destructiveHint false, idempotentHint true). It adds no additional behavioral context beyond annotations, but there is no contradiction.

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, concise sentence with no unnecessary words, clearly structured.

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?

The description lists the specific metadata returned (jti, audience, expiry, IP, user agent), providing clarity on what the user gets despite lacking an output schema.

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?

The schema fully describes the jti parameter, and the description reinforces its role as the identifier sourced from list_jwts, making its meaning unambiguous.

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 it reads a single JWT session's metadata by its id, listing the exact fields (jti, audience, expiry, IP, user agent), and distinguishes from list operations.

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?

It mentions the id comes from scaleway_iam_list_jwts, implying usage after listing, but does not explicitly contrast with other tools or provide explicit when-to-use guidance.

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