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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not explain what "token provenance" means, whether owner resolution requires elevated permissions, or what the tool returns when no owner is found.

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 six-word phrase with zero filler, and the object of the operation is front-loaded. It is efficient but under-specified rather than genuinely concise, providing no structure to hang behavior or parameters on.

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?

An output schema exists, so return-value explanations are not required. Even so, for a tool with a required account ID, a hidden operation mode, and a pattern-constrained context token, the description leaves the agent without enough to invoke it confidently or interpret what it is really doing.

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?

Schema description coverage is 0% across three parameters, and the description supplies no parameter information at all. Most damaging is the undocumented "operation" parameter: its default is "pull" but no alternative values are named anywhere, and the constrained "connection_context" pattern is likewise unexplained.

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 phrase names a verb ("Find") and two targets ("account owner" and "token provenance"), so the intent is roughly graspable. However, "token provenance" is undefined jargon, and nothing distinguishes this from siblings like accounts_get_account_detail or account_get_profile, which an agent could plausibly pick instead.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives, despite ~130 sibling tools including several that appear to return account-level information. The agent gets no signal about when this tool is the right choice.

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