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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds modest value by specifying this reads the 'saved' (persisted) state and enumerates the identity fields, but discloses nothing about permissions or response shape beyond what annotations 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?

Two tight sentences with the identity of the resource front-loaded and the field list immediately following. 'Same settings as Studio SEO/GEO' is slightly insider phrasing but earns its place as a mental-model anchor.

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 no output schema, the description usefully enumerates the returned fields, and annotations cover the safety profile, so the agent has enough to call it correctly. Missing only any note on required auth or how app_id is obtained.

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 description coverage is 0% and the description never mentions app_id, so it does not compensate for the gap. However, the single parameter is a self-evident identifier for an app-scoped metadata read, so the omission causes little practical ambiguity.

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 (saved public HTML-shell identity) and enumerates the fields returned (name, description, language, image URLs/dimensions). This is clear enough to distinguish it from most siblings, but it never explicitly differentiates itself from the adjacent get_app_detail or its write counterpart set_app_metadata, so it stops short of a 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?

The description offers no when-to-use guidance and names no alternatives. The only contextual hook, 'Same settings as Studio SEO/GEO,' explains equivalence to another surface rather than telling the agent when to pick this tool over get_app_detail or get_app_status.

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