Get one JWT session by id

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds value by listing the specific metadata fields returned (jti, audience, expiry, IP, user agent), which is beyond what annotations convey. It does not contradict any annotations.

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, well-structured sentence that front-loads the verb 'Read' and immediately conveys the tool's purpose. Every word adds value, with no redundancy or filler.

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 simple read tool with one parameter, rich annotations, and no output schema, the description is complete. It specifies the operation, the input (id), and the output fields. The parameter description in the schema complements the tool description. No gaps remain.

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% with a clear description for the 'jti' parameter. The description adds meaning by stating the tool reads metadata by id and lists the fields returned, which is not present in the schema (no output schema). This helps the agent understand what information will be retrieved using the parameter.

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 explicitly states the verb 'Read' and the resource 'JWT session's metadata', listing the specific fields (jti, audience, expiry, IP, user agent). It clearly distinguishes from siblings like scaleway_iam_list_jwts (list all) and scaleway_iam_delete_jwt (delete) by specifying this is a read operation for a single session by id.

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?

The description implies usage context by stating the tool reads by id and the parameter description notes the id comes from scaleway_iam_list_jwts. While it does not explicitly state when not to use or list alternatives, the simplicity of the tool and presence of sibling tools make the intended use clear. Slight improvement would be to explicitly mention that this is for retrieving metadata after listing.

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