token_info

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

With no annotations, the description must carry the burden of behavioral disclosure. 'Informations sur le token' implies a read-only query and the listed fields clarify what will be inspected. However, it does not explicitly state side effects, authentication expectations, or that no data is modified.

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 concise sentence that front-loads the resource and immediately lists the key output categories. There is no filler or redundant information.

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 informational tool with an output schema, the description is largely complete: it names the resource and what information is available. The main missing piece is clarifying the relationship to token_permissions, but that gap is primarily a usage-guidance issue rather than a completeness issue for invoking the tool.

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 parameter explanations are unnecessary. The description usefully enumerates the token attributes returned, and the output schema handles structural details. This matches the baseline for a no-parameter tool.

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 resource ('le token') and the specific information returned (type, expiration, application, scopes). It lacks an explicit verb like 'get' or 'retrieve', and it does not explicitly distinguish itself from the sibling 'token_permissions', so it falls just short of a 5.

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 gives no guidance on when to choose token_info over alternatives. In particular, the sibling tool token_permissions likely overlaps on scopes/permissions, but the description does not clarify the difference or provide any selection criteria.

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