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

No annotations are provided, so the description must disclose all behavioral traits. It does not mention return behavior, side effects, rate limits, or any operational details. The only additional information is billing cost ('1 Credits'), which is not a behavioral trait.

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 extremely brief, but this is under-specification rather than conciseness. It contains only metadata ('Group: User', 'Billing per call') and lacks all functional substance, so it fails the purpose of a description.

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?

With 11 parameters, 0% schema description coverage, no annotations, no output schema, and no description content, the tool is completely under-specified. An agent cannot infer what the tool does, what parameters mean, or what the response looks like.

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?

With zero schema description coverage and 11 parameters, the description provides no help. Parameters like 't', 'show', 'after', 'before', and 'sr_detail' are ambiguous; the description does not explain any of them or their relationships, leaving the agent to guess.

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 'User Posts Group: User. Billing per call: 1 Credits.' provides no verb or resource statement; it reads as a metadata label rather than a functional description. The name 'get_user_posts' implies retrieving posts for a user, but the description does not clearly state this or differentiate from siblings like 'get_user_comments' or 'get_user_overview.'

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?

There is no guidance on when to use this tool versus alternatives, no context about required inputs, and no mention of prerequisites or typical use cases. The description is entirely silent on usage scenarios.

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