get_tryton_context

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

With no annotations provided, the description carries the behavioral disclosure burden. It does indicate that the tool performs a non-mutating 'check' of two specific things: the connection and model access. However, it does not explain what happens on failure, whether any external system interaction occurs, or what conditions determine whether access is 'required.'

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, immediately front-loaded with the verb and object, containing no filler or redundancy. It is appropriately minimal for a zero-parameter diagnostic tool.

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 that there are no parameters and an output schema exists, the description is nearly sufficient for invocation. However, it leaves 'required' access unexplained and provides no context about when this check is useful, so an agent is left to infer the intended workflow.

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?

Because the tool has zero parameters, there is nothing for the description to add beyond what the schema already documents. The baseline score of 4 applies here since parameter semantics are not applicable.

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 tool checks the configured connection and required Tryton model access, which is a distinct diagnostic purpose compared to the product, lot, and stock sibling tools. The phrase 'required Tryton model access' is slightly ambiguous about which models or requirements are meant, so it stops just short of a top score.

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 guidance is provided for when to use this tool versus alternatives, such as running it first when connection or permission errors are suspected. The context is only implied by the tool's name and purpose, not explicitly stated.

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