feedly_action

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

No annotations are present, so the description must disclose behavioral traits. It does not mention whether actions are destructive, authentication requirements (though api_key parameter hints), rate limits, or return behavior. This is a critical gap for a tool with multiple actions.

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 extremely short (one sentence), which is concise but at the expense of essential information. It is not well-structured; it simply lists actions. Overly brief descriptions that omit critical details are not considered effective conciseness.

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 tool has 6 parameters, no schema descriptions, no annotations, and no output schema, the description is severely incomplete. It fails to provide context on how the tool works, parameter relationships, or expected results, making it nearly unusable without external knowledge.

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 has 0% description coverage, and the description adds almost no parameter meaning. It indirectly lists possible action values but does not explain api_key, stream_id, query, count, entry_ids. The agent cannot understand how to use parameters from the description.

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 it performs Feedly actions and lists five specific actions, giving some clarity. However, it does not explain the overall purpose or what Feedly is, and the verb 'Perform' is vague. It is minimally adequate to distinguish from sibling tools, but lacks specificity.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, context, or exclusions. The agent is left to infer, which is insufficient.

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