Get VIPMP docs page

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds that it fetches 'full content' and relies on a path, but it does not describe invalid-path behavior, caching effects, or response characteristics. For a read-only retrieval tool this is acceptable but not rich.

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?

The description is compact: one clear opening sentence, a short Args block, and a practical example. Every sentence earns its place, and the most important information is front-loaded.

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 a single parameter, an output schema, and annotations covering the operational safety profile, the description provides everything an agent needs to invoke the tool correctly. It also explains how to discover valid paths, which addresses the main practical uncertainty.

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?

The schema has 0% description coverage for the only parameter, so the description must compensate. It does so by naming the parameter's purpose and giving a concrete example path, while also directing agents to list/search tools for valid values. This is sufficient for a single parameter, though it relies on an example rather than stricter format rules.

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 uses a specific verb ('Fetch') and a specific resource ('full content of a specific Adobe VIP Marketplace documentation page'), which clearly distinguishes it from list/search siblings and from content-specific siblings like get_vipmp_schema or get_vipmp_code_examples. The title reinforces the same message without ambiguity.

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 explicitly instructs agents to use list_vipmp_docs() or search_vipmp_docs() to find valid paths, which provides clear prerequisite guidance. It does not mention when not to use this tool, but the sibling names and the first sentence make the intended use case fairly obvious.

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