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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real behavioral facts beyond them: that first-account partner status is restricted to Lab desktop, that existing accounts get a neutral review, and that the MCP never emits an aff_id (an important disclosure for anyone advising a signup).

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?

A single sentence, front-loaded with the purpose and then the three sub-topics it covers, closed by the invocation trigger. Every clause carries information; nothing is redundant or padding.

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?

With an output schema present, the description need not explain return values, and for a zero-parameter informational tool it adequately states both scope and when to call it. It is complete enough to invoke correctly, though it could name related tools to route the agent more sharply.

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 the baseline is 4; there is nothing for the description to clarify beyond the empty schema. Parameter semantics are not a source of ambiguity here.

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 states a specific verb ("Explique" / explain) and a specific resource: the post-proof TradingView partner journey, including first-account partner status (Lab desktop only), neutral review of existing accounts, and why the MCP never emits aff_id. This is clearly distinct from action siblings like export_to_tradingview or get_lab_desktop_handoff, but no sibling is named explicitly, so the differentiation is implied rather than stated.

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?

"À appeler avant de conseiller une inscription TradingView" gives an explicit trigger condition for invoking the tool. It does not list when-not-to-use cases or name alternative tools, but the usage context is concrete and unambiguous for an informational tool.

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