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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds value with the concrete outcome ('removed from the social media scheduler') and the auth requirement ('requires a Picorn access token'), which annotations do not convey.

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 tight clauses with the core outcome front-loaded and the auth prerequisite appended. No wasted language, though the auth note could be folded more naturally.

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 single-parameter cancel tool whose annotations already cover the destructive/open-world profile and with no output schema, the description covers outcome and auth adequately. The only real gap is that fileId semantics remain undocumented in both schema and description.

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 0% for the single required fileId parameter, so the schema provides no semantics. The description only implies that the fileId identifies 'a file' but adds no format, source, or retrieval guidance to compensate for 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?

The description states a specific verb and resource: cancel the scheduled post of a file, clarifying that it is removed from the social media scheduler. This clearly distinguishes the inverse of picorn_posts_schedule, though it never names that sibling explicitly.

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?

It gives a timing condition ('before it is published'), which implies when the tool applies. However, it offers no explicit when-not guidance, alternatives, or error conditions (e.g., what happens if the post is already published).

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