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

No annotations are provided, so the description carries the full burden. It adds only 'Billing per call: 1 Credits' and does not disclose authentication expectations, return behavior, pagination, side effects, or failure semantics.

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 and front-loaded, with no wordy filler. The first sentence repeats most of the tool title, but it is still concise and includes useful billing context.

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 5-parameter tool with no output schema and no annotations, this description is far too sparse. It lacks return behavior, use cases, auth/model expectations, pagination details, and any information that would let an agent safely sense and invoke the tool correctly.

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 just 20%; only auth_token has a real description. The tool description neither explains cursor, userId, proxyUrl, resFormat, nor how they relate to getting UserArticlesTweets, so the agent must guess even basic parameter usage.

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 says 'Get UserArticlesTweets tweets info' and 'Group: userTweets', giving a clear verb and resource category. However, it does not explain exactly what UserArticlesTweets returns or how it differs from similar siblings like userTweetsV2 or tweetTimeline.

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 'when to use' guidance is present. The description provides a group label and billing metadata only, which does not help an agent decide between this tool and the many sibling tweet/user-timeline tools.

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