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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself,' which resolves the apparent conflict between the name 'edit' and the read-only annotation. It also discloses the return shape (screens, buttons, fields) and the required follow-up tooling. It stops short of saying what happens if the store item doesn't exist or how the target item is identified given zero parameters.

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?

Purpose is front-loaded, but the sentence is overstuffed with channel boilerplate ('from ChatGPT, Claude or any AI agent') and the closing API note with a dated audit ('checked 17 Oct 2026') is filler that does not help an agent decide or invoke. Trimming would sharpen the core instruction.

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 guidance tool with no output schema, the description covers what it returns and what to do next, which is the critical information. The one unresolved question — how the specific store item is targeted — is left implicit.

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 and schema coverage is 100%, so there is no parameter meaning to add; baseline 4 applies. The description could have explained how the target store item is determined without arguments, but that is a design gap rather than a description omission.

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 first sentence names a specific verb and resource (edit store item) and immediately reframes it as a guidance tool that 'returns how to do it in StreamElements step by step.' That reframing is essential, since 'edit' would otherwise imply a mutation. It does not, however, distinguish itself from the sibling cotlet_app_guide, which likely serves a similar advisory role.

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?

Clear usage flow: call this to get the step-by-step procedure, then execute it with cotlet_browser_* tools in the Cloud Browser. What's missing is any exclusion or alternative — nothing says when to use cotlet_app_guide instead, or what to do if the user wants a direct API path.

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