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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds real value beyond them by clarifying that reading rules is inert with respect to automation state and outbound messaging, defusing the likely confusion with create/trigger siblings.

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?

Two sentences, no filler, with the resource and scope front-loaded and the non-side-effect clarification second. Every clause 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?

For a read-only listing tool with no output schema, the description covers what is listed, the scope, and the absence of side effects. It does not describe pagination or result volume, which is a minor gap given there is no output schema to carry that.

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?

With 3 parameters at 67% schema coverage, the schema does most of the work for workspace_id and leaves brand_id and the sparse 'query' override undocumented. The description's phrase 'for the selected workspace' reinforces workspace_id but adds no syntax or meaning for the other two parameters. 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 (List) and resource (social inbox automation rules) scoped to a workspace, and notes the content of the returned rules (trigger and response settings). It is distinguishable from create/update/delete_inbox_automation, but it does not explicitly differentiate itself from nearby read siblings such as get_inbox_items.

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?

Usage is implied rather than stated: the tool is for inspecting configured automation rules. The line 'Reading rules does not enable them or send messages' clarifies the reading context but stops short of naming when this is preferred over alternatives or what prerequisites apply.

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