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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them by stating the return content (screens, buttons, fields) and explicitly that it "opens nothing by itself," preventing an agent from assuming it mutates AppFolio state.

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 compact sentences, front-loaded with the action and immediately followed by the critical clarification about what it returns and what it does not do. The "from ChatGPT, Claude or any AI agent" phrase is mild padding but does not obstruct the core message.

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?

With no output schema, the description properly compensates by describing the return value at a useful level of detail, and it explains that a separate browser tool set performs the actual work. The remaining gap is that it never positions itself relative to the AppFolio work-order siblings, which matters given several overlapping names.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly does not invent parameters or suggest inputs the schema rejects (additionalProperties: false).

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 names a specific verb and resource ("Schedule work order in ... AppFolio") and, crucially, clarifies that the tool returns step-by-step instructions rather than performing the action — a distinction the bare name does not convey. It stops short of naming the closest siblings (appfolio_create_work_order, appfolio_assign_work_order) whose scope overlaps scheduling.

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 follow-on path — after getting the recipe, execute with cotlet_browser_* tools in the AppFolio Cloud Browser — which is genuinely useful sequencing guidance. However, there is no guidance on when to choose this over create/assign work order siblings, and no stated exclusions or prerequisites.

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