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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the non-obvious clarification that 'a link never performs the change on navigation' — important because the listed use cases involve deletion and removal wording that could otherwise be read as destructive. It adds the OAuth requirement, which annotations do not cover. It does not describe pagination or what the screen handle looks like, but with annotations and an output schema that 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?

Four sentences, front-loaded with the triggering scenario, followed by alternatives, a parameter hint, a behavioral caveat, and an auth note. Every sentence carries information; the only mild density cost is the long enumeration of removal scenarios in the first sentence.

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 navigation tool with five parameters, an output schema, and full annotation coverage, the description covers purpose, alternatives, parameter provenance, the read-only nature of navigation, and OAuth. Nothing essential to correct invocation appears missing, though the semantics of each destination enum value are left to the schema.

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 80%, so the schema already documents id, blockId, imageId, listingIds. The description adds real value for blockId by specifying its provenance ('current blockId from get_profile') and implicitly maps the destination enum values to the use cases. It adds little beyond the schema for id, imageId, and listingIds, so the baseline of 3 is appropriate.

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 establishes that this tool surfaces a specific dashboard screen for a task (photos, profile story/URL edits, removal/deletion review) rather than performing the mutation itself, and it names sibling tools (manage_listing_images, manage_profile_images) it is not. The core verb 'opens a dashboard screen' is only implied through 'needs a precise dashboard screen', so it is clear but not crisply front-loaded as verb+resource.

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?

It gives concrete triggers (adding listing/profile photos, editing story or URL, reviewing deletion/removal/unlink/list-member-removal) and routes photo-adding to manage_listing_images or manage_profile_images instead. It also states the prerequisite of passing the current blockId from get_profile. It stops short of an explicit when-not-to-use statement for the remaining destination values.

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