publish_verification_due

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

The description implies a read-only check but does not explicitly state side effects, return value, or error behavior. With no annotations, it fails to disclose whether the tool is pure, what it returns (e.g., boolean), or how edge cases (invalid timestamps, missing 'now') are handled.

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, grammatically correct sentence with no wasted words. It front-loads the verb and clearly states the core functionality, achieving maximum conciseness for the information it conveys.

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?

Given the absence of annotations, output schema, and parameter descriptions, the description should compensate by providing comprehensive context. It fails to explain the return value, the role of 'now', or any behavioral nuances, leaving significant gaps for a tool with only two parameters.

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%. The description mentions 'nextVerificationAt' but does not explain its format or semantics, and completely ignores the optional 'now' parameter. The agent receives no help understanding parameter meaning, especially since the schema provides no descriptions.

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 clearly states the tool's purpose with a specific verb ('Check') and resource ('publish schedule'), and specifies the condition ('due for verification based on its nextVerificationAt'). This distinguishes it from sibling tools like publish_job_verify, which likely verifies job status rather than schedule due-ness.

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 is provided on when to use this tool versus alternatives. The description does not mention workflow context, prerequisites, or any exclusions. Sibling tools exist but are not referenced, leaving the agent without decision criteria for tool selection.

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