postifys_media_status

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

The verb 'Poll' indicates a read-style status-checking behavior, which is useful because no annotations are provided. However, the description does not disclose what the response represents, whether the call blocks or can be repeated, or any errors/lifecycle caveats.

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?

One tight sentence with no filler; the operation, resource, and parameter are stated up front. Nothing could be cut without losing meaning.

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 simple one-parameter poll tool, the description is minimally viable, but it lacks return-value, workflow, and sibling-relationship context that would help an agent decide when to call it and what to do with the result. No output schema exists to fill that gap.

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 description explicitly relates mediaJobId to the job being polled, adding a minimal semantic role beyond the bare schema property. It does not explain how the ID is obtained or what format is expected, but the single self-descriptive parameter limits the 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?

Identifies a specific operation (poll) and resource (a Postifys media job), and names the required identifier. It is clear, but it does not explicitly contrast with sibling tools like postifys_get_post_status, relying on the 'media' vs 'post' distinction in the resource name.

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?

No guidance on when to use this tool versus alternatives such as postifys_media_upload or postifys_get_post_status. No prerequisites, such as a mediaJobId from a previous upload, or conditions under which polling should stop, are mentioned.

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