get_post_summaryRetrieve a summary of a Circle community post by post ID, optionally choosing the account credentials to use.
Get Post Summary. Reads community data.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Named private Circle account; selects credentials, not a remote community ID. | |
| post_id | Yes | Post ID |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds no behavioral context beyond restating that it reads data, such as auth requirements, rate limits, or what happens with private versus public posts.
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, but the second sentence "Reads community data" is vague and does not earn its place. It is under-specified rather than appropriately concise.
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?
For a read tool with no output schema, the description should clarify what a "post summary" contains or when to request it. Instead it gives no return-value context and no usage context, leaving the agent to infer everything from the schema and annotations.
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%, and both parameters are documented in the input schema. The description adds no meaning beyond the schema, so the baseline of 3 applies.
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 repeats the title ("Get Post Summary") and adds only the vague phrase "Reads community data." It does not specify what kind of summary is returned, nor does it distinguish this tool from siblings like get_post or list_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?
There is no guidance on when to use get_post_summary versus get_post, list_posts, or any other sibling. The only usage signal is the generic verb "Reads," which does not explain context, prerequisites, or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.