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

With no annotations, the description carries the full burden of behavioral disclosure, but it reveals nothing about side effects, output format, read-only status, or rate limits. The only extra information is billing cost, which is not behavioral transparency.

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 short, but it is under-specified rather than concise. The two phrases 'User Overview Group: User' and 'Billing per call: 1 Credits' waste the limited space without conveying the tool's function, failing the 'every sentence earns its place' test.

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 tool with 3 parameters, no output schema, and no annotations, the description should explain the tool's purpose and parameter semantics. It does neither, making the tool effectively opaque to an AI agent.

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 schema has 3 parameters with 0% description coverage, and the description adds no meaning to 't', 'sort', or 'user'. Without any explanation of how these parameters affect the query, the agent cannot correctly construct a call.

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 only states 'User Overview Group: User' and a billing note, with no verb or resource indicating what the tool actually does. It does not differentiate from sibling tools like get_user_comments or get_user_posts, and it fails to state that it returns an overview of a user's activity.

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?

No guidance is provided on when to use this tool versus alternatives. The description offers no context about use cases, prerequisites, or exclusions, leaving the agent without any basis for tool selection.

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