App data form

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

Annotations already declare readOnlyHint=true, covering the read-only nature of the operation. The description adds that it returns an HTML form and specifies the endpoint, but does not disclose other behavioral traits such as authentication requirements, rate limits, or the exact structure of the returned form. With annotations present, this is acceptable but not rich.

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?

The description is a single, front-loaded sentence that efficiently communicates the action, resource, endpoint, and purpose. No unnecessary words or redundant information are present.

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 parameterless tool with readOnlyHint annotation, the description fully explains what the tool returns (the HTML form) and why it exists (for CRUD on app data). The output is an HTML form as explicitly stated, so no output schema is needed. The description is complete for a simple form-fetching tool.

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 input schema is an empty object with 0 parameters and 100% schema description coverage. There are no parameters to clarify, so the description correctly does not add parameter information. The baseline of 4 is appropriate for a parameterless tool.

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 'Return the HTML form used to create, modify or delete app data (\`/v2/appdataform\`)'. This specifies a precise verb ('return'), a concrete resource (HTML form), and the operations it supports (create, modify, delete). It is clearly distinguished from sibling tools like banana_appdata_put, banana_appdata_delete, and banana_appdata_get, which perform the actual data operations.

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?

The description implies the tool should be used when the HTML form for app data CRUD is needed, and the sibling tool names (appdata_put, appdata_delete, appdata_get) indicate alternatives that perform the operations directly. However, it does not explicitly say 'use this when you need the form, not the data operation', leaving that inference to the agent.

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