grocy_system_config

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 genuinely new behavioral context by warning that filesystem paths are stripped from the result, which prevents an agent from expecting raw path values. It stops there and says nothing about response size or caching.

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?

Three compact fragments with the resource stated first and the behavioral caveat last; nothing is padded. The bare endpoint string is slightly machine-flavored redundancy but is consistent with an API-mirroring toolset.

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 zero-param read tool with no output schema, the description should hint at the shape of the returned config object, since "all config settings" is a large and undocumented structure. It covers the safety and one transformation (path stripping) but leaves the agent guessing about what keys come back.

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 and the schema is empty with 100% coverage, so there is nothing for the description to disambiguate. Baseline of 4 applies.

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?

"All Grocy config settings" plus the concrete endpoint (GET /api/system/config) makes the resource and read nature unmistakable. It stops short of distinguishing itself from adjacent siblings such as grocy_system_info, grocy_system_localization, or grocy_system_time, so an agent must infer the boundary.

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?

Usage is only implied: an agent deduces it should call this when it needs configuration values. There is no explicit 'use this instead of grocy_system_info when...' guidance and no stated prerequisites or exclusions despite a crowded system_* family.

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