grocy_calendar_sharing_link

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond a REST endpoint: 'public' hints the resulting URL is unauthenticated and sensitive, but there is no note on secrecy, rotation, stability of the link, or whether calling it has side effects such as persisting a token.

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?

One short, front-loaded sentence. The trailing 'GET /api/calendar/ical/sharing-link.' is largely redundant endpoint plumbing that adds no decision-relevant information, but the whole entry is only two lines.

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?

No output schema exists, so the description should say what is actually returned (a plain URL string, possibly absolute vs. relative). That key fact is missing, leaving the agent to guess the response shape even though annotations cover the read-only nature of the call.

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 disambiguate. Baseline 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?

States the specific resource clearly: a public sharing link for the iCal calendar. An agent can tell this generates/returns a URL rather than calendar data itself, which separates it from grocy_calendar_ical, though the distinction is left implicit 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?

No guidance on when to call this versus grocy_calendar_ical (which presumably returns the actual iCal feed). No mention of prerequisites such as whether a link must be generated/rotated first, or what an agent should do with the returned link.

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