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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds no behavioral context. It does not mention pagination, return format, permissions, or any operational characteristics. With annotations present, the description fails to contribute any additional 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 is a single line, but it is under-specification rather than conciseness. It does not earn its place because it adds no information beyond the tool name. It lacks front-loaded content and is essentially empty of meaning.

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?

With a low schema coverage and no description text, the tool is completely under-specified. An agent has no idea what the endpoint returns, what the parameters do, or how to construct a valid request. The output schema exists but the description does not help in understanding it. This is grossly inadequate for a tool with three parameters and nested objects.

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 only 33% (only workspaceId has a description). The path.postId and query parameters (limit, ending_before, starting_after) are undocumented in the schema, and the description provides no explanation of their meaning or usage. The description adds zero value to parameter semantics.

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 the HTTP method and path, which is essentially a restatement of the tool name. It does not state what the tool does beyond the endpoint. No verb or resource explanation is provided, so an agent cannot infer the tool's purpose from the description alone.

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 like get_posts or get_posts_id. The description offers no context for selection, no exclusions, and no mention of related tools.

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