app_clip_advanced_experiences__get

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 agent knows this is a safe read operation. The description adds no substantive behavioral context beyond affirming the read and the ID parameter; it neither contradicts annotations nor reveals additional traits like rate limits or response shapes.

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 exceptionally concise, using one sentence and a method reference. It is front-loaded with the verb 'Read' and carries no filler. Every element serves a purpose, making it ideal for quick agent comprehension.

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?

Given the tool's simplicity, the annotations, and the highly descriptive schema, the short description is sufficient to enable correct invocation. The lack of an output schema is mitigated by the resource name and the parameter descriptions, which indicate response composition. A minor gap is the absence of explicit error/status expectations, but not critical for a read operation.

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 input schema has 100% description coverage, with detailed explanations for the id, include, and fields parameters. The tool description itself adds no parameter-specific details, so the baseline of 3 applies since the schema effectively carries the semantic burden.

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 clearly states the action ('Read') and the resource ('one App Clip advanced experience by ID'), distinguishing it from related operations like create or update. The endpoint reference reinforces the specific singleton read behavior.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that the ID comes from a list call, nor does it exclude cases like listing all experiences. The only implicit hint is the phrase 'by ID', which is insufficient for explicit usage guidance.

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