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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: the exact response shape (import-tool design format, slides vs. a single slide object for IMAGE), inclusion of brand data, and that the call is free.

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?

A single dense sentence with the identifier and return shape front-loaded; nothing is wasted. The phrasing is slightly compressed ('its design in the shape the import tools take'), but it still reads cleanly.

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 an output schema present, the description needn't enumerate return fields, and it still previews the design shape and brand inclusion. For a one-parameter read tool this is essentially complete, with only the sibling distinction left implicit.

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% and the schema already states the parameter is an embedPostId 'not a designId'. The description's mention of embedPostId largely repeats that, adding no format or syntax detail. Baseline 3 is appropriate when the schema does the work.

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?

Names a specific verb (Read) and resource (a post made through the API) plus the key identifier (embedPostId), and characterizes the returned design shape ('slides, or one slide object for an IMAGE'). This is far more specific than the title, though it never names the sibling it is distinct from (e.g. postnitro_get_scheduled_post, postnitro_get_output).

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 it to see what a post says before editing it' supplies a concrete triggering context and even a cost note ('Free'), which is actionable. It stops short of explicit exclusions or naming an alternative when a caller wants a scheduled post versus an API post.

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