List Scheduled Posts

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

No annotations provided; description only states functionality without disclosing behavioral traits like idempotency, error handling, performance implications, or return format. A list read operation's safety is implied but not explicit.

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 sentences, zero waste. Every word adds value: identifies the resource, lists key capabilities concisely. Appropriate for a straightforward list tool.

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?

Adequately covers purpose and filters, but lacks details on return structure (no output schema) or limits beyond the schema's description. Could mention typical data fields returned.

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 100%, so baseline is 3. The description summarizes available filters ('account(s), status, and date range') but adds no new meaning beyond the schema's own parameter 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?

Clearly states 'List scheduled and published posts', which is a specific verb+resource. While it doesn't explicitly distinguish from siblings like repliz_list_content, the focus on scheduled posts provides sufficient differentiation.

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?

Mentions supported operations: pagination and filtering by account, status, date range. Provides clear context for when to use, but lacks explicit when-not or alternative tool guidance.

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