hcm_get_atom_feed

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

The readOnlyHint annotation covers the safety profile, so the description only needs to add behavioral context. It does mention the format switch to XML and the 'dummy' mechanism, but both are vague. The description does not disclose pagination, how 'since' affects results, or whether the feed is a live or stubbed source.

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 short and front-loaded with the core action, which is good. However, 'via dummy' is an unclear and potentially misleading phrase that adds confusion without earning its place.

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, the description should explain return shape and behavior more thoroughly, but it only says 'as JSON entries.' It also fails to address the 'limit' and 'collection' parameters and does not orient the agent among the many atom-related sibling tools, leaving important context missing.

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?

Schema description coverage is low (only 'collection' is described in the schema), so the description must compensate. It does add meaning for 'since' as an ISO filter and for 'format' as controlling JSON vs XML, but it says nothing about 'limit' or the 'collection' filtering behavior beyond the schema's terse enum values.

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 the tool retrieves an Atom feed, with JSON as the default and optional XML format. However, the phrase 'via dummy' is confusing and not explained, which slightly muddies what the tool actually does. It does not explicitly differentiate this tool from sibling Atom-related tools like hcm_list_atom_entries or hcm_detect_changes.

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 given about when to use this tool versus the many closely related Atom feed tools such as hcm_atom_poll, hcm_atom_consume, hcm_list_atom_entries, or hcm_detect_changes. The description implies a basic retrieval use case but provides no exclusions or alternatives.

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