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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral detail beyond the HTTP method and path; it does not mention pagination, filtering behavior, ordering, or response characteristics.

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 and front-loaded, but this is under-specification rather than effective conciseness. A single endpoint string does not meaningfully describe behavior, so the sentence does not earn its place as a useful tool description.

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 a nested query object with filters, pagination parameters, and a required workspaceId, this description is far from complete. The output schema and annotations help, but the description leaves major selection and invocation questions unanswered, especially around filtering and list versus single-post behavior.

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 provides a description only for workspaceId, and the query object's subproperties are self-explanatory only by name. The description adds zero parameter meaning, does not explain the required workspace context, and does not compensate for the 50% schema description coverage.

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 literally 'GET /v1/posts', which mostly restates the tool name and endpoint without explaining what the tool does semantically. It does not state that it retrieves a list of posts, what scope it covers, or how it differs from get_posts_id.

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 about when to use this tool versus siblings like get_posts_id, get_post_history, or get_channels. The description gives no context about whether this is the collection-level list endpoint or a filtered search, so an agent has to guess.

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