grocy_system_localization

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds one useful behavioral fact — the result is scoped to the authenticated user's language — but says nothing about caching, size of payload, or whether it depends on a user setting.

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?

Two short, front-loaded fragments with no filler. The trailing 'GET /api/system/localization-strings' restates the resource as a URL rather than adding information, costing a small amount of signal.

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 trivial no-parameter read the definition is close to sufficient, and annotations carry the safety profile. However, with no output schema, the description never says what the payload looks like (a key-to-string map?), which is the one thing an agent actually needs here.

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 tool takes zero parameters, so there is nothing for the description to explain. Baseline 4 applies; the implicit 'authenticated user language' selector is at least useful context.

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?

States a specific resource and scope: localization strings for the authenticated user's language. That is enough for an agent to distinguish it from the closely named sibling grocy_system_log_missing_localization, though the two are never explicitly contrasted.

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 when-to-use or when-not-to-use guidance; the sentence only describes content plus a raw endpoint path. The near-identical sibling grocy_system_log_missing_localization is not mentioned, so the agent gets no routing help.

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