tocaro_list_groups

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the bot-scoped nature of the list, the query search behavior, pagination ranges, and the format/purpose of the returned group `code`. It does not mention errors or side effects, but for a read-only listing tool this is reasonable.

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?

Three concise, front-loaded sentences with no filler. Purpose comes first, then parameter constraints, then the key output detail about the returned `code`. Every sentence earns 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?

The tool is simple with three optional parameters and an output schema, and the description covers the key invocation details and the cross-tool usage of the returned code. It lacks explicit alternative routing and error/edge-case details, but these are partially mitigated by the output schema and low complexity.

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 0%, so the description must compensate. It adds meaning by explaining `query` as a group-name search and constraining `page` and `per_page` to 1-100. It does not elaborate on page/default semantics, but the property names and defaults make those reasonably clear.

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: it retrieves the list of groups the bot belongs to. It also clarifies the query behavior and the purpose of the returned code, making it easy to distinguish from sibling tools like tocaro_get_group_members or tocaro_search_users.

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?

Gives clear context on when to use this tool: to fetch groups and obtain `code` values for passing to other tools like tocaro_post_message and tocaro_list_todo_lists. It does not explicitly name alternatives or exclusions, but the use case is evident.

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