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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds what the annotations cannot: the required scope (profile:read), the risk classification and the statement of no side effects, which is the useful marginal context. It does not describe response shape or failure modes.

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 sentences plus a compact scope/risk/effects line, front-loaded with the ordering advice that matters most for an agent deciding what to call first. Nothing is padded, though the field enumeration is a long single sentence.

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 no output schema and no parameters, the description carries the burden of saying what comes back, and it does so by listing the returned facets. That is enough for an agent to decide to call it first; only the return structure (shapes, nullable fields) is left implicit.

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, which is the baseline-4 case: there is nothing for the description to disambiguate, and it correctly omits any argument discussion.

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 names a specific verb-and-resource pair (returns the connected identity) and enumerates exactly which facets are returned: user, selected account/operation, Neural operator, connected app, effective scopes and authorized properties. That enumeration separates it from near-neighbours like list_accounts or get_permissions, though it never names those siblings explicitly.

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?

"Chame primeiro para entender o contexto antes de outras operações" gives an explicit ordering instruction with a clear condition (before invoking other tools). No exclusions or named alternatives are given, so it stops short of a 5, but an agent knows exactly when to reach for it.

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