Cloudflare: Get user

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

Annotations already declare readOnlyHint=true, so the trailing "Read-only." adds nothing. The genuinely new disclosure is that the target user is derived from the stored credential rather than from input, which matters for how an agent selects this tool; beyond that, no auth requirements, rate limits, or failure modes are described.

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?

One front-loaded sentence carries the verb, scope, and return fields with no waste. The appended "Read-only." is redundant with readOnlyHint=true and could be dropped.

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?

A simple single-param read tool whose safety profile is covered by annotations and whose return fields are enumerated inline, so it is largely sufficient. The unexplained required "site" parameter is the notable gap, and there is no output schema to fall back on for return shape.

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 single required parameter "site" has 0% schema description coverage and is never mentioned in the description, so the agent must guess that it selects the Cloudflare site context. The description partially implies the user identity comes from the token rather than parameters, but the one param it does have is left unexplained in both places.

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?

States a specific verb and resource ("Fetch the Cloudflare user profile") and scopes it precisely with "authenticated by the stored API token," plus enumerates the returned fields (id, email, username). That scope distinguishes it from the other *_get_user siblings in the catalog, though it never names them 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?

The phrase "authenticated by the stored API token" implicitly tells the agent this tool takes no user identifier and always returns the caller's own identity, which is meaningful guidance. However, there is no explicit when-to-use/when-not statement and no pointer to an alternative for looking up a different user.

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