Compare live and pending metadata

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

The readOnlyHint annotation already establishes this is a safe read, so the bar is lower. The description does add real context beyond the annotations: the fields compared (descriptions, keywords, release notes), the cross-locale scope, and the 'Pro feature' entitlement note. It does not describe diff granularity, ordering, or size limits, so it stays mid-range.

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 short sentences, front-loaded with the core action, and every sentence contributes: the comparison, the field scope, and the entitlement. No repetition of the title or schema.

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 single-parameter read tool this is nearly complete, and with no output schema the description sensibly sketches the return content ('what changed in descriptions, keywords, and release notes across locales'). It still omits how results are structured or whether unchanged locales appear, a minor gap for a diff 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?

Only one parameter exists and schema description coverage is 100%, so the schema already fully documents app_id. The description adds no format or constraint details beyond what the schema carries, making the baseline 3 the correct score.

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 gives a specific verb+resource ('Compare metadata between your live and pending app versions') and enumerates the compared fields, making the tool clearly distinct from mutators like update_version_metadata or set_app_metadata. It stops short of naming any sibling tool outright, so it lands at 4 rather than 5.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. The only usage-adjacent signal is 'Pro feature,' which hints at an entitlement requirement but does not tell the agent when this diff is the right call versus release_preflight or app_details.

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