naukri_session_status

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

No annotations are provided, so the description must carry behavioral disclosure. It states the action is a check, implying no side effects, but it does not specify the return value or behavior when no session exists. It lacks details about how validity is determined, so only partial disclosure is provided.

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 sentence that is front-loaded with the action 'Check'. It is concise, with no filler or redundancy, and every word contributes to the meaning.

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 its zero-parameter simplicity, the description states the purpose clearly. However, without an output schema, it does not describe the return format or possible statuses (e.g., boolean, error), leaving ambiguity about how an agent should interpret results. This is a minor gap for a status-check tool, but it is still incomplete for an agent that needs to react to the output.

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 tool has zero parameters, so schema coverage is 100% by default. The description adds no parameter details, but none are needed. Baseline 4 applies because no parameters exist and the description need not compensate.

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 the verb 'Check' and the resource 'whether there's a currently valid, logged-in Naukri session'. It distinguishes from sibling tools like naukri_login and naukri_close_session, which are actions not status checks. The purpose is specific and unambiguous.

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 does not explicitly state when to use this tool versus alternatives. It implies usage via its purpose (checking session status before operations), but does not mention that it should be used before authenticated actions nor exclude alternatives. Guidance is implied, not explicit.

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