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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: the required App Store Connect key, where it is configured, and the 'Free' cost signal. It does not describe return format or pagination, but for a read-only tool covered by annotations this is a minor gap.

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?

Front-loaded with the returned fields, then the prerequisite and the fallback alternative. Dense but every clause carries information; the field enumeration is long but useful for recognizing the tool's scope.

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 one-parameter read-only tool with no output schema, the description compensates well by listing returned fields, the auth requirement, and the alternative when unauthenticated. The only real hole is the unexplained appId parameter.

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?

There is a single parameter, appId, with 0% schema description coverage, and the description never mentions or explains it. With low coverage the description should compensate, but it only indirectly implies app context via 'the results app' and does not say whether appId is required, optional, or defaults to the current app.

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?

States a specific verb (read) and resource (every locale's App Store Connect metadata), enumerating the exact fields returned (name, subtitle, keywords, promotional text, description, what's new) and distinguishing the version being prepared from the live one. An agent can tell what this returns without opening any schema.

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?

Explicitly names the prerequisite (founder's App Store Connect key connected on the App Store page) and the fallback when it is missing: 'use app_audit with the repo's fastlane metadata.' The selection condition and the named alternative are both present, leaving nothing to inference.

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