Authentication Status

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

With no annotations, description discloses that it checks credential configuration and session viability. It implies read-only behavior ('check'), but does not explicitly state it is non-destructive or if it has side effects. Adequate for a simple status check.

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 key verb. Every word adds value. No unnecessary detail.

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?

Tool is simple (0 params, has output schema). Description sufficiently conveys purpose. Could mention that it returns a boolean or status object, but output schema covers that. Complete for its 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?

Schema has 0 parameters with 100% coverage trivially. Description adds meaning by specifying what exactly is checked (credentials configured, session creation). Baseline for 0 params is 4, and description provides additional context.

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 verb 'Check' and resource 'Ninova credentials' and 'fresh session'. Distinguishes from sibling tools like obs_auth_status which checks OBS credentials, and refresh_session which creates a new session.

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?

Description implies this should be used before other actions to verify auth, but does not explicitly state when to use versus alternatives like obs_auth_status or refresh_session. No exclusions or context provided.

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