list_settings_notifications_gotify

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the HTTP GET endpoint but no additional behavioral context such as auth requirements, rate limits, or response handling. For a zero-parameter read operation this is acceptable, though not a rich disclosure.

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?

The description is two concise lines with no filler. The core action is front-loaded, and the endpoint is a useful supplementary detail. Every element earns its place.

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 no-parameter, read-only tool with an output schema and safety annotations, the description is complete enough. An agent knows the resource, the HTTP method, and the safe read-only nature of the operation without needing additional context.

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 has zero parameters and the schema is empty, so there are no parameter semantics for the description to clarify. The baseline for zero-parameter tools is 4, and the description does not need to compensate for any undocumented inputs.

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 states a specific verb and resource: 'Get Gotify notification settings.' This clearly distinguishes it from other notification-provider settings tools and from create_settings_notifications_gotify. The included endpoint reinforces the exact operation, though it adds little beyond the tool name itself.

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 implied rather than explicit. The verb 'Get' and the readOnlyHint annotation suggest this is the tool to use for reading Gotify settings, but the description does not explicitly contrast it with create_settings_notifications_gotify or other list_settings_* siblings. No alternatives or when-not-to-use conditions are mentioned.

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