fomo_get_clan_feed

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Clan activity feed' implies a read-only feed but says nothing about ordering, pagination, time range, authentication, or side effects.

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 very short les, but brevity here is under-specification rather than efficiency. It adds almost no information beyond the tool name and does not front-load any actionable context.

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 annotations, zero schema coverage for three parameters, and no output schema, the one-line description leaves critical context missing, including what the feed items look like, how pagination works, and what the id parameter refers to.

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?

Input schema coverage is 0%, and the description does not mention the required 'id' or optional 'limit' and 'feedTypes' parameters. An agent cannot infer what values to pass or how they affect the returned feed.

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 'Clan activity feed' is a noun phrase that essentially restates the tool name 'fomo_get_clan_feed' without adding a clear verb or explaining what the feed contains. It only weakly distinguishes this from siblings like get_clan_holdings or get_clan_leaderboard.

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?

There is no guidance on when to use this tool, what type of query it suits, or how it differs from sibling feed-related and clan-related tools. The description gives the agent no basis for choosing this tool over alternatives.

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