list_uib_data_brokers

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

The description adds domain context (data brokers are data sources for pages) but no behavioral detail beyond what annotations already provide. readOnlyHint and openWorldHint already indicate a read-only, open-world operation. The description doesn't disclose pagination, return format, or filtering semantics.

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?

A single, front-loaded sentence with no filler. It concisely states the action and resource, making every word valuable.

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?

As a list operation with two optional parameters and no output schema, the description gives minimal context about return shape or limit usage. It's adequate for a simple listing but leaves gaps around result structure and pagination, which are not covered by annotations.

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 50%: page_sys_id is documented, but limit is not. The description itself doesn't mention or explain any parameters. It adds no semantic value for limit, leaving it solely defined as a number with no context, and page_sys_id is only explained in schema, not reinforced here.

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 uses the specific verb 'List' and identifies a distinct resource type 'UI Builder data brokers', with a clarifying parenthetical '(data sources for pages)'. This clearly distinguishes it from siblings like list_uib_pages or create_uib_data_broker.

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?

No explicit when-to-use guidance is given. The parenthetical implies the tool is for enumerating page data sources, but there are no alternatives or exclusions mentioned. Usage is only implied, not explicitly clarified in relation to other tools.

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