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

With no annotations, the description carries full burden for behavioral disclosure. It states it gets data, but does not mention side effects, return format, pagination, or any limitations. The mention of credits is a billing detail, 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 very short and includes extraneous billing information ('6 credits', 'Billing per call: 1 Credits') that is not essential for understanding the tool's function. It is concise but not optimally focused on the tool's purpose.

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?

Given the lack of output schema and minimal parameter info, the description is incomplete for an agent to determine how to call the tool correctly. It does not explain the output, the meaning of parameters, or any constraints, making it insufficient for effective use.

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 provides zero parameter descriptions, and the description does not explain any of the five parameters (page, apiKey, proxyUrl, resFormat, screenName). Since schema coverage is 0%, the description should compensate but does not, leaving the agent without any parameter context.

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 clearly states the tool's purpose: retrieving deleted tweets for a given user. It is distinct from sibling tools like analytics or blocks, so the verb/object combination is specific.

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 does not provide any guidance on when to use this tool vs. alternatives, nor does it mention prerequisites, typical use cases, or parameter requirements. It only mentions credits and billing, which are not usage guidelines.

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