grocy_stock_location_entries

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. Beyond that the description only restates the REST path; it says nothing about whether entries are paginated, whether zero-stock products are included, or what shape the entries take.

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 fragments with no filler, and the resource is front-loaded. The raw endpoint sentence is borderline but does add a small amount of orientation.

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 simple read tool with full schema coverage and annotations, this is still thin: it does not clarify the return content or how it differs from related stock tools, leaving the agent to guess what 'entries' means in this domain.

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 coverage is 100% and the single location_id parameter is documented in the schema, so the baseline is 3. The path template {locationId} merely echoes the schema and adds no new meaning.

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?

Names the resource (stock entries) and scopes it to a location, but uses a noun phrase with no verb, so it is unclear whether this lists raw entry rows or aggregates. It is partially distinguishable from siblings like grocy_stock_entry or grocy_stock_overview only by the 'at a location' qualifier.

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 indication of when to use this over grocy_stock_entry, grocy_stock_overview, or grocy_stock_volatile. The endpoint path hints at a per-location read, but nothing explicit routes the agent among alternatives.

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