get_user_summary

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

With no annotations provided, the description must carry the behavioral burden. 'Anonymous' usefully discloses auth expectations and 'Get' implies a non-mutating operation. However, it does not describe the response shape, data freshness, error behavior, or whether any user can be looked up.

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?

The description is two short sentences with no filler. The core purpose is front-loaded, the parenthetical clarifies scope, and 'Anonymous' is an efficient behavioral note.

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?

For a simple one-parameter read tool, the description covers the main purpose and auth context. But with no output schema, no annotations, and no guidance about when to prefer this over sibling tools, the overall picture is only minimally complete.

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 input schema has zero description coverage and only a bare 'username' string property. The description's 'a user's activity summary' adds little meaning beyond the property name; it does not explain username format, case sensitivity, or how missing/invalid usernames are handled.

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 uses a specific verb and resource: 'Get a user's activity summary' with explicit contents '(posts, likes, badges)'. This makes the tool's function clear. It does not explicitly contrast itself with siblings like get_user_profile or get_current_user, but the activity-summary focus is still distinctive enough.

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 description includes 'Anonymous,' which implies this can be called without authentication and provides some usage context. However, it lacks any explicit guidance on when to choose this tool over alternatives like get_user_profile or search_users, and no when-not-to-use conditions are given.

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