list_groups

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

With no annotations, the description carries the full burden. It does disclose the response shape (id and name), which is useful, but says nothing about authentication requirements, rate limiting, or whether the list is paginated or truncated — for a "List all" tool the all-vs-page question is the key behavioral unknown. The trailing dangling fragment "Known groups: " suggests the intended content (a static group enumeration) was cut off, further weakening disclosure.

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?

Front-loaded and efficient: purpose, return shape, rationale, and workflow example in three tight sentences. It loses a point for the trailing incomplete "Known groups: " fragment, which is dead weight as written.

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?

An output schema exists, so return values needn't be re-explained, and with no parameters and no nested objects the surface area is small. The rationale-plus-workflow framing is exactly what an agent needs to place this tool in a multi-step plan; the only omission is any note on result size or pagination behavior.

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 and additionalProperties is false, so there is nothing for the description to clarify; the baseline for a 0-param tool is 4. The description correctly implies no filtering arguments are accepted.

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?

States a specific verb and resource ("List all Freshdesk agent groups") and immediately narrows the scope by declaring the return payload ("Returns group id and name"). No sibling tool does this, so an agent can distinguish it without opening any schema.

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?

Explicitly states the purpose-context ("Use this to find the group_id for filtering tickets by team") and then names the sibling to combine it with via a concrete chained workflow: list_groups → find id → search_tickets group_id=<id>. This is about as clear a when-to-use signal as a one-line description can carry.

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