hcm_detect_changes

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

The readOnlyHint=true annotation aligns with the read-only nature of 'summarize'. The description adds useful context about client-side filtering and the optional timestamp, but it does not disclose pagination behavior, output shape, or how 'recent' is determined.

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 a single, compact sentence with no filler, and it front-loads the core action. The phrasing 'Atom/change entries' and 'client-side filter on feed' is somewhat jargon-heavy but still concise.

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 three parameters, the description does not explain what the summarized result looks like, what 'collection' refers to, or how 'limit' behaves. The lack of sibling differentiation and parameter context leaves an agent with an incomplete picture for calling the tool correctly.

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 coverage is only 33%, with solely 'since' described. The description reinforces that 'since' is an optional ISO timestamp, but it adds no meaning for 'limit' or 'collection', leaving those parameters effectively undocumented in both the schema and 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 a clear action ('summarize') and resource ('recent Atom/change entries'), and mentions the optional 'since' timestamp. However, it does not explicitly differentiate this tool from closely related siblings like hcm_list_atom_entries or hcm_atom_poll.

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 versus alternatives. The phrase 'client-side filter on feed' implies it reads feeds, but it never contrasts with hcm_list_atom_entries or hcm_atom_poll, so an agent cannot decide confidently between them.

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