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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, and the description correctly adds behavior the annotations cannot express: anonymous ids that have been claimed are redirected to their canonical profile, and bot-tagged traffic is filtered out of the activity summary unless include_bots is true. Those two facts materially change how an agent interprets the returned numbers. It does not discuss pagination or limits on the activity summary, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core action and result, then the two behavioral caveats. No filler or restatement of the tool name beyond the unavoidable "Get returns". Slightly awkward lead-in phrasing but structurally sound.

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 the description rightly does not explain return values, and it uses the freed space for redirect and bot-filter behavior. The main residual gap is that no parameters are required, yet the description never says what happens if called with an empty argument set. For a read-only lookup of this complexity that is a minor omission.

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 coverage is only 33%, with just project_id documented in the schema, so the description needs to carry weight. It does explain id as the "pug profile id" and gives real semantics for include_bots (bot traffic excluded from the activity summary unless true), but it says nothing about project_id's role or the id format, and with zero required parameters it never clarifies which combination is valid. Partial compensation lands at 3.

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 opens with a specific verb and resource ("Get returns a single user profile") and scopes the lookup to "its pug profile id", which implicitly separates it from the external-id sibling. It also enumerates what comes back (identity properties plus an activity summary), so the agent knows the payload shape. It stops short of naming an alternative tool explicitly, so full sibling differentiation is not spelled out.

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?

Usage is only implied: the "by its pug profile id" phrasing tells the agent this is the id-based lookup rather than the external-id variant. There is no explicit when-to-use or when-not-to-use statement, and no mention of prerequisites or of what to do when several profiles match. The include_bots sentence is a behavioral rule rather than selection guidance.

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