util_jwt_inspect

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

No annotations provided. Description indicates a read-only decode operation and mentions 'quickly', suggesting performance, but does not disclose error handling, authentication needs, or side effects.

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?

Single sentence, front-loaded with verb and resource. Efficient but could be structured with separate lines for purpose and usage.

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 decode tool, the description lacks parameter guidance, return format, and error behavior. Output schema absent; parameter incomplete.

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 has one generic parameter 'arguments' (object with additionalProperties) with 0% description coverage. Description adds no meaning to the parameter; no explanation of expected keys like 'token' or format.

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?

Clearly states verb 'Decode', resource 'JWT claims', and intended use cases 'auth debugging, routing, and token inspection'. Distinguishes from sibling utilities which do not decode JWTs.

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?

Implies usage context ('for auth debugging, routing, and token inspection') but provides no explicit when-not-to-use or alternative tools. Lacks guidance on prerequisites.

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