get_uib_page

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds that the tool returns layout and child elements, but does not disclose other behavioral traits such as required permissions or rate limits. With annotations covering safety, the bar is lower, but minimal extra context is provided.

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?

The description is a single, front-loaded sentence (14 words) that immediately conveys the verb and resource. No unnecessary words or repetition.

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 description tells what the tool returns (details, layout, child elements). Given the simplicity of the tool (1 param, no output schema, strong annotations), it is adequately complete. Could be improved by noting if the page must be deployed or if there are access restrictions.

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% with a single parameter 'sys_id' described as 'UIB page sys_id'. The description does not add any additional meaning or constraints beyond what the schema already provides. Baseline 3 applies since coverage is high.

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 clearly states the tool retrieves details of a specific UI Builder page, including layout and child elements. It uses a specific verb (Get) and resource (UI Builder page), and distinguishes it from sibling tools like list_uib_pages (which lists pages) and create/update/delete operations.

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?

The description implies use when needing details of a single page, but does not explicitly state when to use this tool versus alternatives like get_portal_page or get_record. No guidance on prerequisites or limitations.

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