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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the tool is read-only, any rate limits, billing details beyond a generic credit count, or side effects. The billing note is not a behavioral trait.

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 brief, but that brevity stems from under-specification rather than effective conciseness. The single sentence is essentially a label and billing note, offering no substantive information, so it reads as a placeholder.

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 one parameter and no output schema, the description is the only guide for agents. It fails to state what the tool does, what it returns, or any constraints, making it wholly incomplete for even a simple GET operation.

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 description does not explain the 'id' parameter at all. Schema description coverage is 0%, meaning the description adds zero value beyond what the schema already provides, and even the schema only includes a title and example.

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 'Community Post Details Group: Community Post' merely restates the tool's name and category without explaining the action (e.g., retrieves details) or the resource. It does not differentiate from sibling tools like get_v1_community_post_comments, which also relates to community posts.

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 guidance is given on when to use this tool vs alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without any indication of when this is the appropriate choice.

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