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

Annotations already mark this as read-only and non-destructive. The description adds useful context by listing the concrete return fields and noting that the same schedules appear in the web app. It does not disclose ordering or pagination, but that is acceptable for a zero-parameter read operation.

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?

Three short sentences with the main action and return fields front-loaded. The web-app context sentence is mildly nonessential but adds useful user-facing context. No fluff or redundancy.

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 zero-parameter read-only list with no output schema, this is effectively complete. The description states what the tool returns, gives user-facing context, and provides a clear use condition. Missing pagination details are minor given the tool's simplicity.

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 is empty with 100% schema description coverage, so there are no parameters that require explanation. Baseline 4 applies for zero-parameter tools, and the description appropriately focuses on return value semantics instead.

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?

States the exact action and resource: 'List all recurring post schedules.' It enumerates the returned fields, which makes the operation unambiguous, and clearly differentiates this from list_posts and schedule mutation tools like create_schedule/update_schedule.

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?

Gives explicit trigger context: 'Use this when the user wants their recurring posting schedules.' It does not name an explicit alternative or when-not condition, but there is no close sibling for listing schedules, so the context is sufficient.

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