subscription_group_localizations_v2_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: no read-only confirmation, no auth/scope requirements, no pagination or error behavior, no statement that a missing id yields 404. A bare URL template adds zero 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 a single path repeated twice in parentheses, which is pure redundancy rather than concision. Nothing is front-loaded because there is nothing substantive to front-load.

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 fetch with four parameters and no output schema, the description should at minimum say what resource is returned and that sparse fieldsets/includes can expand it. With no annotations and no return documentation, an agent has to open the schema and guess the semantics of include and fields_*.

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 baseline is 3: id, include, and the two sparse-fieldset parameters are all documented in the schema itself. The description adds no syntax or format detail beyond that, but the schema already 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 only restates the HTTP path already encoded in the tool name (subscription_group_localizations_v2_get_instance), duplicated verbatim in parentheses. It conveys 'fetch one subscription group localization by id' only by inference from the URL, not by stating purpose in words. No differentiation from siblings such as subscription_group_localizations_get_instance or subscription_group_localizations_v2_update_instance.

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 prerequisites, and no mention of alternatives. An agent cannot tell from this text when to prefer this v2 instance fetch over the v1 sibling or over the relationship endpoints (subscription_groups_subscription_group_localizations_get_to_many_related). Only the implicit 'GET by id' is available.

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