get_user_profile

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

With no annotations, the description carries the full burden and does well: it discloses read-only behavior, that no auth is required, and enumerates the returned fields (ranking, avatar, bio, submission stats, platform progress). It doesn't cover rate limits or failure behavior for unknown usernames, so not a full 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 tight sentences, front-loaded with the purpose and return contents before the sibling routing guidance. Every sentence earns its place with no repetition of the schema.

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?

Though there is no output schema, the description lists what is returned, and the auth/read-only posture is explicit despite missing annotations. The only thin area is edge-case behavior (invalid or nonexistent usernames), which is not addressed.

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 100% and already states the username is case-sensitive and requires no auth. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies for a single fully-documented parameter.

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 ('Retrieves any user's public profile by username') and immediately scopes it as public/read-only. It also names the sibling it must not be confused with, so an agent can distinguish it from get_user_status without opening either schema.

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?

Gives both sides of the routing decision: use this for looking up other users or public stats, and use get_user_status (requiring auth) for verifying the current session user. It even adds an exclusion ('not for looking up arbitrary users'), leaving nothing to inference.

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