freshrss_get_token

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

With no annotations, the description carries the full burden. It adds the behavioral note that the tool is 'usually called automatically when needed,' which tells the agent this is primarily an internal helper. It does not mention prerequisites such as prior authentication or any side effects, but for a simple zero-parameter getter this is a minor gap.

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 sentences with no wasted words. The core operation is front-loaded, and the second sentence provides useful usage context without redundancy.

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-parameter helper tool with an output schema, this description is mostly complete. It could be more explicit about when manual invocation is warranted, but the automatic-call note sufficiently covers typical usage.

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 input schema has no parameters, so there is nothing for the description to add. The zero-parameter 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?

The description clearly states a specific verb ('Get') and resource ('edit token'), and identifies the purpose as supporting write operations. It does not explicitly differentiate from freshrss_authenticate, but 'edit token' is reasonably distinct from authentication.

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?

The phrase 'Usually called automatically when needed' implies that direct invocation is normally unnecessary, which is useful context. However, it does not specify when a manual call would be appropriate or explicitly contrast this tool with siblings like freshrss_authenticate.

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