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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no mention of what a missing id returns, whether the post is scoped to the caller's space, or any freshness/visibility behavior.

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?

Six words, front-loaded with the resource and key, with zero filler. It is efficient, though the terseness borders on under-specification rather than tight communication.

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 single-parameter read tool with no output schema, the description should at least sketch what a 'market post' contains or how failures are signaled. As written it leaves the agent to infer everything beyond the fact that an id is required.

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 0%, so the bare 'id: string' property carries no documentation of its own. The description's 'by id' does confirm the id identifies a market post, but it does not clarify whether this is a market post id versus a user/space id or what format it takes, so it only partially compensates for the coverage gap.

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 phrase 'One market post by id' identifies the resource (market post) and the lookup key (id), so the basic operation is inferable. However it never names the verb explicitly and gives no differentiation from close siblings like market_search, market_close, or market_respond, leaving an agent to guess its role in the family.

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 statement of when to use this versus market_search (finding posts) or market_close/market_respond (acting on them). The only implied usage comes from the name and the 'by id' phrase, which is thin guidance for a family with several market* tools.

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