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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: no return shape (one merged payload vs. two lists), no result limits, no ordering, no error behavior.

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 sentence, front-loaded with the useful part ('Combo action: return both...'). The trailing shell-alias parenthetical is token waste for an API agent and could be dropped without loss.

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?

With no output schema and no parameters, the description carries the burden of explaining what comes back. It says which two datasets are returned but not how they are structured or whether either can be empty, leaving a meaningful gap for a combined-result tool.

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 the baseline is 4. The CLI-style hint (`ff agentitter` / `ff a8r`) is consistent with a no-argument call, though it adds no semantic value for an agent.

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 concrete outcome — returning mutual friends plus favorited authors in a single call — which resolves the opaque name 'ff'. However, it never names the obvious siblings list_friends and list_favorites, so the agent must infer that this is the combined shortcut for those two tools rather than a distinct resource.

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 'in one call' implies this is the batch alternative to invoking the individual list tools, which is usable guidance. But there is no explicit when-to-use/when-not, no mention of whether it's preferred over list_friends + list_favorites, and no prerequisites stated.

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