Show Image Post

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 fully covered elsewhere. The lone sentence "Reads community data" adds no behavioral context beyond what the annotations provide — no note on required permissions, error behavior, or what a missing post returns.

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?

Two short fragments are brief but not concise in the meaningful sense — they are under-specified rather than efficient. Neither sentence carries information the agent can act on.

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 tool requiring both space_id and post_id with no output schema, the description should at least hint at what is retrieved (media, caption, author, comments). Instead it provides nothing an agent needs beyond what the name and schema already imply.

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% (account, post_id, space_id are all documented, including the non-obvious note that account selects credentials rather than a community ID). With the schema doing all the work, the description's silence on parameters meets the baseline of 3 but adds no value.

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?

"Show Image Post" merely restates the tool name and title, and "Reads community data" is a vague generic gloss that applies to dozens of siblings. Nothing distinguishes it from get_post, list_image_posts, or duplicate_image_post.

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 when-to-use guidance at all — no mention of when to prefer this over list_image_posts (for enumeration) or get_post (for text posts). The agent is left to infer the context entirely from the name.

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