update_app_info

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

Indicates mutation ('update') and mentions 'draft' scope, but no annotations provided. Does not disclose side effects, idempotency, error behaviors, or required app state. Moderately transparent but incomplete.

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?

Single sentence, concise and front-loaded. No unnecessary words, though could be structured (e.g., list parameters) for clarity. Efficient use of space.

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 13 parameters, no annotations, and no output schema, the description is too brief. Missing prerequisites (e.g., need app_id), explanation of 'draft', return values, or error scenarios. Incomplete for a complex mutation 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?

Schema coverage is 69%, and description lists parameter groups matching schema fields but adds no extra meaning. Does not explain optionality (required=0) or parameter interactions. Baselines at 3 due to moderate coverage.

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?

Description clearly states 'Update app metadata in the AppGallery Connect draft' and lists specific fields (name, description, category, ratings, support contacts, privacy policy). It distinguishes from sibling tools like update_app_file_info or update_language_info.

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?

No explicit guidance on when to use this tool versus alternatives. No mentions of prerequisites, when not to use, or contrasts with other update tools. Implies use for metadata updates but lacks direction.

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