app_clip_default_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 disclosure burden, and it discloses nothing: no auth requirements, no note that this is a read-only single-resource fetch, no error behavior for a missing id, and no explanation of how the include/fields/limit parameters change the response shape.

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 brevity comes from under-specification rather than efficiency; the parenthetical duplicate of the same path is pure waste, and no informative content is front-loaded because there is none.

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?

An eight-parameter fetch tool with no annotations, no output schema, and a description consisting only of a URL leaves the agent without any behavioral or contextual grounding for correct invocation.

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%, so all eight parameters including the include relationships and sparse-fieldset options are already documented in the schema. The description adds no semantics beyond the schema, which is the baseline-3 case 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 is a restatement of the HTTP path and endpoint, duplicating the tool name rather than describing intent in prose. A reader can infer it retrieves one App Clip default experience, but the sentence adds no information beyond the name and offers no distinction from siblings such as app_clip_default_experiences_release_with_app_store_version_get_to_one_related.

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 statement of when to call this tool, what prerequisites exist (an id of an existing default experience), or which sibling relationships tools should be used instead to fetch related resources. Usage is only weakly implied by the 'GET .../{id}' form.

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