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

Annotations already declare readOnlyHint and destructiveHint=false, yet the description reinforces safety ('Nothing is posted') and adds non-obvious behavior: the output renders in the Suara viewer rather than as raw data, and each post's status can be one of five enumerated states. It stops short of noting limits, ordering, or default date range.

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?

Front-loaded with the usage trigger, followed by return contents and the single-post shortcut; every sentence is functional. The parenthetical status list is long but earns its place by defining the vocabulary an agent will see in results.

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 no output schema, the description carries the return-value burden and does it: caption, hashtags, day, status, and viewer rendering. It leaves the actual date window ambiguous ('this week' vs. 'what's coming up') and says nothing about result volume or pagination.

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 coverage is 100%, so both parameters are already documented, including images and postId's carousel-slide nuance. The description only restates postId ('Give postId to see one post') and says nothing about the images flag or its default, so baseline 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?

States a specific verb and resource ('see this week's posts') plus the detail/answer shape, and 'Read only. Nothing is posted.' separates it from mutation siblings like approve_post and send_to_suara. It never names an alternative sibling explicitly, so it falls short of full differentiation.

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?

'Use this when the signed-in owner wants to see this week's posts, what's coming up, or what a post looks like' gives clear trigger conditions and also signals the single-post mode via postId. No when-not-to-use conditions or named alternatives are provided.

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