app_infos__update

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

Annotations already indicate idempotentHint=true and destructiveHint=false, and the description adds the PATCH method which aligns with these traits. However, it does not disclose any additional behavioral context such as return behavior, auth requirements, or side effects beyond what the annotations and PATCH method imply.

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 extremely concise, consisting of two short sentences ('Update an app info' and the HTTP endpoint). It is front-loaded and contains zero unnecessary words, earning full marks for efficiency.

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?

The tool has a well-structured schema and annotations, but no output schema and no mention of the response format. For a simple update operation, the description is adequate but leaves the agent to infer what the PATCH returns. Additional clarity on the response would improve completeness.

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 schema provides 100% coverage with descriptions for both parameters (id and body), so the baseline is 3. The description itself does not add any parameter-level meaning, relying entirely on the schema.

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 'Update an app info' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes itself from sibling tools like app_infos__get by the verb 'update', though it does not elaborate on what aspects of app info can be updated.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The description is purely a statement of action, leaving the agent to infer usage context from the tool name and schema.

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