create_schedule

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention permissions needed, whether schedule names must be unique, what happens on conflicts, or the return behavior. The single hint about rules/filter categories referencing schedules is useful context but far from sufficient for a mutation tool.

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, front-loaded with the core action, no redundancy. The second sentence adds scope context efficiently.

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 required-parameter mutation tool with no annotations and no output schema, the description is incomplete. It should state required permissions, prerequisites (e.g., profile existence, timezone format expectations are covered by schema but usage expectations are not), and what the created schedule enables.

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 the schema fully documents all six parameters including formats and examples. The description adds no parameter-level detail beyond implying a profile association, which is already in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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+resource: 'Create a time-based schedule on a profile.' It clearly distinguishes from sibling list_schedules and delete_schedule, but does not mention the parent resource ('profile') handling or how it differs from create_rule beyond the 'time-based' qualifier.

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 explicit when-to-use guidance or prerequisites are provided. The second sentence hints at integration with rules/filter categories, which implies usage context, but there is no statement about when this tool should be chosen over create_rule or whether the profile must already exist.

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