app_clip_default_experience_localizations_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. The HTTP method 'GET' weakly signals a read-only, non-destructive operation, but there is nothing about authentication requirements, error behavior for unknown ids, or what a successful response contains.

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 half its content is a verbatim duplicate of the other half in parentheses, which is pure waste. Nothing useful is front-loaded because nothing useful 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 single-resource getter with five parameters and no output schema, the description should at least confirm the retrieval semantics and the id-based lookup. Full schema coverage mitigates the parameter gap, but the definition is effectively 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%, so the schema already documents 'id', 'include', and the three 'fields_*' sparse-fieldset parameters. The description adds nothing beyond that, which is the baseline expectation 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 tool name and endpoint path ('GET /v1/appClipDefaultExperienceLocalizations/{id}') twice, with no verb-plus-resource phrasing an agent could use to distinguish it from siblings. It implies a single-resource retrieval, but that is inferred from the URL shape rather than stated.

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 guidance on when to use this tool versus alternatives such as app_clip_default_experiences_localizations_get_to_many_relationship or app_clip_default_experience_localizations_app_clip_header_image_get_to_one_related. No preconditions, no exclusions, no context.

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