delimit_content_schedule

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

Despite no annotations, the description declares 'Side effects: read-only' and mentions the internal call to ai.content_engine.get_content_schedule. This fully discloses behavioral traits beyond what structured fields would provide.

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 well-structured with clear sections and no fluff. Every sentence adds value, and it is appropriately sized for a no-parameter 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?

Given zero parameters and presence of an output schema (implied by 'Returns'), the description fully covers what the tool does, what data it returns, and when to use it. No gaps remain.

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?

Input schema has zero parameters with 100% coverage, and description explicitly states 'Args: None.' No additional param semantics needed; baseline for 0 params is 4.

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 starts with 'View the upcoming content schedule (queued + pending + recent) (Pro).' This specifies the verb and resource clearly. It distinguishes from siblings by explicitly stating when not to use and sibling contrast.

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?

Explicit 'When to use:' and 'When NOT to use:' sections are provided. Alternatives like delimit_content_publish and delimit_content_queue are named, giving clear guidance on when to use this tool vs others.

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