ksef_test_connection_check

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

Description claims 'persist readiness' which implies a state change, contradicting the readOnlyHint=true annotation. This is a serious inconsistency. No additional behavioral traits disclosed 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?

Single sentence is concise and front-loaded, but lacks essential detail. The description is too brief to be fully informative, though it avoids verbosity.

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?

Despite having output schema and annotations, the description is incomplete. It fails to explain the tool's behavior beyond a vague authentication/persist claim, and contradicts annotations. Missing clarity on what 'persist readiness' means.

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 optional boolean parameter 'use_real_nip_ack' with 0% description coverage. The description does not explain its meaning or effect, providing no value beyond the schema.

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 'Authenticate' and resource 'KSeF TEST' with purpose 'persist readiness before invoice XML generation'. It distinguishes from siblings which focus on other operations like submitting or validating invoices.

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 guidance on when to use this tool versus alternatives like ksef_session_status or ksef_get_capabilities. Only implies usage before invoice generation but lacks comparative context.

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