Validate platform-integration JWT

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

Annotations already denote read-only and non-destructive. Description adds value by detailing the returned 'profile' object contents (language, ui_labels), providing practical behavioral context beyond 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?

Two succinct sentences, no redundancy. Purpose stated first, followed by return value details. Every word earns its place.

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?

Given simplicity (1 param, output schema exists), description fully covers functionality and return value. Annotations cover safety. No gaps identified.

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?

With 0% schema description coverage, the description compensates by explaining the JWT must come from 'generate_jwt', adding semantic meaning to the parameter beyond just 'string'.

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?

Clear verb 'verify' and resource 'JWT'. Immediately distinguishes from sibling 'generate_jwt' by stating it verifies previously issued JWTs. Mentions returned profile structure, adding specificity.

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?

Explicitly states it is for verifying JWTs from 'generate_jwt', implying a sequence. No explicit when-not-to-use or alternatives, but the purpose is clear enough given sibling context.

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