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

readOnlyHint=true already declares the safety profile, and the description reinforces it with 'READ-ONLY — GET only', a minor restatement. It does add real context on the request shape (base is /v3, method is GET {path}), but says nothing about rate limits, error responses on invalid paths, or pagination behavior of raw results.

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 tight clauses, front-loaded with the escape-hatch role before the constraint and the API template. No padding or redundant sentences.

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?

For a raw passthrough tool with no output schema, the definition supplies the essential invariants: /v3 base, GET-only, path and params shapes, and the fallback role. It omits only secondary details like error handling on malformed paths, which is forgivable for a raw HTTP escape hatch.

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 100%, so both 'path' and 'params' are already documented, including format and the JSON-string encoding. The description's inline path examples add marginal flavor but no semantics beyond the schema; baseline 3 applies.

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 (issue a raw GET) and resource (any Chat Platform API v3 path), and explicitly frames itself as a fallback for endpoints 'not wrapped by a dedicated tool'. This distinguishes it immediately from the dedicated sibling tools like sendbird_get_group_channel or sendbird_list_messages.

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 a clear when-to-use condition ('paths not wrapped by a dedicated tool') and concrete example paths, plus the when-not implied by the escape-hatch framing. It stops short of naming which dedicated sibling to prefer for a given resource, so the routing decision still requires the agent to scan the sibling list.

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