ExtendScript guide

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds what the payload actually contains — ES3 rules, helpers, match names — which helps the agent decide whether fetching is worthwhile. It does not state the return format or approximate size, a minor gap for a content-retrieval 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 compact clauses with zero filler: the first declares the return contents, the second gates usage. The core purpose is front-loaded ahead of the usage caveat.

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 retrieval tool with no output schema, the description covers what is returned and when to call it. The only missing pieces are the response's form (raw text vs. structured) and rough length, which matter somewhat when deciding to spend context on it.

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 zero parameters, so the baseline is 4 and there is no parameter semantics for the description to carry. Nothing is missing on this dimension.

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 — 'Returns the After Effects ExtendScript cheat sheet' — and enumerates its contents (ES3 rules, helpers, common match names). It also explicitly distinguishes itself from the dedicated tools, notably ae_run_script, so an agent can separate it from siblings without opening anything.

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?

Gives both sides of the decision: use it 'before writing complex ae_run_script code' and it is 'not needed for the dedicated tools.' That names the trigger condition and the exclusion, leaving nothing to infer.

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