check_publish_status

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

With no annotations, the description must carry the full burden of behavioral disclosure. The verb 'Read' indicates a non-destructive operation, but it does not disclose return format, error behavior on missing ids, or any side effects. The single sentence provides minimal behavioral context beyond the inherent meaning of 'read'.

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?

The description is a single, front-loaded sentence: 'Read a saved publish record by id.' It contains no filler or redundancy. Every word contributes to the meaning, making it appropriately concise for a trivial read operation.

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?

The tool is simple with one parameter and no output schema. The description tells what it does, but does not explicitly state what it returns (e.g., the full record or just the status). Given no output schema, a brief mention of the return value would improve completeness. It is adequate but has clear gaps.

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 input schema has zero description coverage for the only parameter 'id'. The description adds that the record is read 'by id', clarifying that 'id' is the identifier of the publish record. This is minimal but sufficient given the parameter is self-descriptive; it could have specified the id format or origin.

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 description uses a specific verb 'Read' with a clear object 'saved publish record' and method 'by id'. This clearly distinguishes it from sibling tools like publish_post or check_platform_auth, which have different purposes (writing or checking auth).

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?

The description implies its usage: use it to read a saved publish record when you have its id. However, it provides no explicit guidance on when to use this tool versus alternatives like list_platforms or publish_post, and no mention of prerequisites or context.

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