app_clip_advanced_experiences_get_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not that this is a read-only fetch, not idempotency, not auth requirements, not error behavior for a missing id. The endpoint string alone is not behavioral context.

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?

It is short, but the content is duplicated verbatim in parentheses, which is pure waste rather than conciseness. Nothing meaningful is front-loaded because nothing meaningful is present.

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 simple GET with full schema coverage and no output schema, an agent still lacks any description of the returned resource or its relationships (appClip, headerImage, localizations) beyond the parameter names. The definition is technically callable but substantively empty.

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 100% (7 parameters, each with a description), so the schema already documents id, include, fields_*, and limit_localizations. The description adds nothing beyond that, which meets the baseline of 3 when the schema does the heavy lifting.

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 merely restates the HTTP endpoint twice: 'GET /v1/appClipAdvancedExperiences/{id} (GET /v1/appClipAdvancedExperiences/{id})'. It conveys retrieval of one resource by id only implicitly through the path, adding no semantic detail about what an 'app clip advanced experience' is or how it differs from siblings like app_clip_advanced_experiences_update_instance. This is tautological relative to the tool name.

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 when-to-use guidance, no mention of alternatives, and no conditions or prerequisites. The agent gets no signal about why it would call this instead of the collection or relationship variants.

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