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

No annotations are provided, so the description must disclose side effects, safety, and behavior. It does not mention any behavioral aspects such as read-only nature, pagination handling, authentication needs, rate limits, or what happens with missing parameters. The only 'behavioral' note is 'Billing per call: 1 Credits', which is trivial and does not aid safe invocation.

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 conciseness is not the issue; under-specification is. It contains two phrases that are largely redundant with the title and adds only billing information. There is no front-loaded value or structured content, making it closer to the 'Process' example of under-specification rather than efficient brevity.

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 tool has 3 parameters, no output schema, no annotations, and a trivial description, the context is wholly incomplete. It does not explain what the feed contains, how pagination works (though cursor is mentioned in schema), how limit affects results, or what user_id refers to. An agent cannot infer the tool's full capabilities or expected response without external knowledge.

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 100%, so the baseline is 3. The description adds no extra meaning to the parameters (limit, cursor, user_id) beyond what the schema already provides. Since the schema is complete, the description does not diminish comprehension, but it also does not augment the parameter semantics with context like typical ranges or relationships.

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 essentially repeats the title and group, and does not explicitly state a verb or action like 'retrieve' or 'list'. It hints at content ('Posts') but fails to clarify what the tool does or how it differs from sibling feed tools such as get_v2_feed or get_v1_feed_home. The purpose is only implied by the name, not explained.

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. The description only includes group and billing info, with no mention of use cases, prerequisites, or exclusions. Sibling tools like get_v2_profile_cameos or get_v2_feed are not referenced, making it impossible for an agent to decide when to invoke this tool.

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