jan3_session_info

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

No annotations are provided, so the description carries the full burden. It clearly states 'non-sensitive info', implying read-only and safe. It lists the fields returned. However, it does not disclose error conditions (e.g., session not found) or authentication requirements. Given the simple read-only nature, transparency is good overall but not exhaustive.

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. Could be slightly improved by explicitly noting the input parameter, but overall well-structured for its length.

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?

Low complexity (one parameter, no output schema). Description covers what info is returned (list of fields). Missing return format details or error handling would be nice but not critical for a simple info retrieval tool. Adequate given the tool's simplicity.

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?

Input schema has one required parameter 'email' (format email) with 0% description coverage. The description does not mention 'email' or explain how it identifies the session. It adds no meaning beyond the schema's type/format, failing to compensate for the missing schema descriptions.

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?

Description clearly states the verb 'Return' and the resource 'non-sensitive info about a persisted JAN3 session'. It lists specific fields (base_url, created_at, captcha_exempt, token previews), which distinguishes it from sibling tools like jan3_list_sessions (which lists sessions) and jan3_user_info (likely user-level info).

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?

No explicit when-to-use or when-not-to-use guidance. The description implies it provides session details, but does not compare to alternatives like jan3_list_sessions or mention prerequisites or context (e.g., session must exist). Purpose clarity partially compensates, but explicit guidance is missing.

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