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

With no annotations, the description carries full behavioral weight and delivers a lot: the POST-per-tick mechanism, the 5-field UTC cron semantics, the x-plinth-cron-secret auth header, the /api/cron/ caller restriction, and the paused-by-default behavior outside production unless enabled is true. Gaps remain around required permissions and error behavior on an invalid schedule, but this is well above average disclosure.

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 dense sentences with the core action front-loaded and zero filler. Every clause (auth header, path restriction, paused default, declarative alternative) earns its place.

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 6-param creation tool with no annotations and no output schema, the description covers the critical runtime behavior an agent needs. It stops short of permission requirements and failure modes, but nothing essential for a correct invocation is missing.

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 coverage is 67%, and the description adds genuine meaning beyond it: it explains the schedule format (5-field, UTC), the security implication of the path, and—most valuably—the semantics of the undocumented 'enabled' param (default paused outside production). The 'name' and 'project' params get no added context.

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 a specific verb and resource ('Schedule a job') and immediately clarifies the mechanism (Plinth POSTs to path on each tick). The purpose is unambiguous against the cron.* sibling set, though it never explicitly distinguishes itself from cron.run, cron.resume, etc.

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?

Implied usage is clear (create a scheduled job), and it mentions the declarative alternative in plinth.json 'crons'. However, it gives no explicit when-to-use guidance relative to siblings like cron.run or cron.resume, and no prerequisites for choosing the API over the declarative route.

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