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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context beyond that: it requires authentication and explicitly states that secret keys are never exposed, which is meaningful security behavior for an API-application listing tool. Pagination or ordering behavior is not described, but the safety and data-visibility profile are clear.

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?

Two dense sentences with no filler: the first establishes the authenticated user context, and the second lists returned fields and the secret-key exclusion. It is appropriately sized, though it could be slightly more front-loaded by leading with the listing action itself.

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?

For a zero-parameter, read-only listing tool with no output schema, the description supplies the necessary return-field overview and explicitly notes what is not returned (secret keys). Authentication context is also provided. It is nearly complete, with only minor gaps such as ordering or result size.

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 takes zero parameters, so there are no parameter semantics to explain. The baseline for 0 params is 4, and the description does not create any parameter-related confusion.

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 identifies the resource precisely: the connected user's API applications, with the exact fields returned (nom, description, moyens acceptés, qui paie les frais, date). It distinguishes the tool from write siblings like creer_application and supprimer_application by framing it as a read of existing applications, though it does not explicitly name those alternatives.

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?

It gives a clear usage condition: for the logged-in Tchin user, merchant or individual, with connection requested the first time. However, it does not explicitly say when to choose this over other application-related siblings or describe any exclusions beyond the implied read-only scope.

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