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

With no annotations present, the description must disclose behavior, but it only names the platform. It does not mention what data is returned, whether it is read-only, any side effects, or required credentials. The agent is left completely in the dark.

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 short, but this is under-specification rather than conciseness. It fails to convey essential information, so it does not earn its place as a useful 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?

Even for a one-parameter tool, the description is incomplete. It does not state the return value, whether it scrapes a profile or posts, or how it relates to sibling tools. Given the large family of scrapecreators tools, this is critically inadequate.

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 already fully describes the only parameter 'handle' as 'Truth Social username' (100% schema description coverage). The description adds no extra meaning, but the baseline for high schema coverage is 3, and there is no gap to compensate for.

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 is simply 'Truth Social' – a platform name. It lacks a verb or resource, so it does not state what the tool does (e.g., scrape, fetch, list). It is a tautology of the tool name, which already contains 'truth_social'.

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 usage context is provided. There is no indication of when to use this tool versus siblings like scrapecreators_truth_social_webhook or scrapecreators_twitter. The description gives no guidance on scenarios or alternatives.

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