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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful context beyond the annotations by saying it contains the SDK, rules, examples, test/save steps, and is 'Free'.

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?

It is a single front-loaded sentence that immediately states the use case and then enumerates what the guide covers. The trailing 'Free' is brief and adds a useful constraint without wasting space.

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 guide with no output schema, the description gives enough context: when to read it, what it contains, and how it relates to testing and saving. It could be slightly more complete by clarifying that it returns guidance rather than performing automation changes, but nothing essential 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?

The tool takes no parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly avoids suggesting any inputs.

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 clearly states this is a read-first guide for building scheduled automations and lists its contents: the script SDK, rules, examples, and test-then-save steps. It distinguishes itself from action-oriented siblings like cotlet_automation_save and cotlet_automation_test by framing itself as prerequisite reading, though it does not use an explicit verb like 'returns documentation'.

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?

It gives a clear triggering condition: 'Read first when the user wants a job to repeat on a schedule (every N minutes, daily, when something new appears).' This tells the agent when to select it, but it does not explicitly state when not to use it or name alternative guide tools such as cotlet_app_guide.

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