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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with the explicit promise that it 'opens nothing by itself,' which is exactly the reassurance an agent needs before proceeding. It also discloses the shape of the return value (screens, buttons, fields). The trailing fragment 'AppFolio's official API: Partly' is cryptic and adds little behavioral certainty.

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 sentences, front-loaded with the action and immediately followed by the crucial 'returns instructions, does nothing' clarification. Every sentence carries weight except the closing 'AppFolio's official API: Partly,' which is vague and would be better as a clear statement of coverage or removed.

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 takes on the job of describing the return, and it does so adequately (step-by-step screens, buttons, fields) while naming the follow-up tools needed to complete the task. A brief note on whether the guidance is account-state dependent, or how it relates to the create/schedule siblings, would close the remaining gap.

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 beyond the schema to explain. Baseline for a parameterless tool is 4; the description correctly does not invent inputs and the call signature is unambiguous.

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 resource (work order assignment in AppFolio) and then reveals what the tool actually does: returns step-by-step in-product instructions rather than performing the action. This distinction is critical and stated cleanly. It never names the adjacent tools (create_work_order, schedule_work_order) to draw the boundary, so the differentiation is left implicit.

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 real workflow: call this to get the screens/buttons/fields, then use cotlet_browser_* tools to actually perform the assignment in the Cloud Browser. That is meaningful when-to-use context. It does not say when to prefer this over appfolio_create_work_order, appfolio_schedule_work_order, or cotlet_app_guide, nor any precondition for when it is inapplicable.

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