notification-updateGotify

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

Annotations set idempotentHint=true and openWorldHint=true, but the description adds no behavioral context. It does not mention side effects, required permissions, or output, so the agent lacks essential transparency for a mutation-like update operation.

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 too short (merely the endpoint) and fails to convey purpose, usage, or parameter context. It is under-specified rather than concise, wasting the opportunity to aid the agent.

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?

Given the complexity (15 parameters, no output schema), the description is grossly incomplete. It lacks any elaboration on behavior, return values, or parameter roles, making it nearly useless for an AI agent to invoke correctly.

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?

With 0% schema description coverage and 15 parameters (including many booleans), the description provides no meaning for the parameters. The agent cannot infer what fields like appBuildError, databaseBackup, or decoration control, making correct invocation unlikely.

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 is only 'POST /notification.updateGotify', which restates the tool name and endpoint path without explaining what the tool does. It does not specify the verb (update), resource (Gotify notification), or differentiate from sibling tools like notification-updateCustom or notification-testGotifyConnection.

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 is provided on when to use this tool versus alternatives. It does not state prerequisites, scope, or exclusions, leaving the agent to guess.

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