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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but 'Post' reveals nothing about whether this is a read, write, or scrape operation, or what side effects might occur. This is a complete lack of 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 consists of a single word, which is under-specified rather than concise. It does not earn its place because it contributes no information beyond the tool name, and there is no structure or front-loading of useful content.

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?

Despite being a simple tool with one parameter, the lack of annotations, output schema, and meaningful description makes it incomplete. The context from sibling tools suggests this is part of a scraping suite, but the description offers no clarity on return values or behavior, leaving significant gaps.

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 description coverage is 100%, with the 'url' parameter described as 'The URL of the LinkedIn post to get'. The tool description itself adds no parameter detail, but the schema already provides sufficient meaning, so the baseline score of 3 is appropriate.

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 just 'Post', which is a noun and tautologically restates the tool name. It does not specify a verb or resource, making it impossible to distinguish from similarly named tools like scrapecreators_post_get or scrapecreators_posts_get.

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 its many siblings, such as scrapecreators_post_get or scrapecreators_posts_get. The description provides no context, prerequisites, or alternatives, leaving the agent without usage direction.

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