get_portal_page

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, indicating safe, idempotent read operations. The description adds minimal behavioral context beyond stating 'Get details' and 'including its layout', but does not contradict annotations (no contradiction found).

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, brief sentence that communicates the core purpose without redundancy. It is appropriately sized for a simple retrieval tool, though it could be slightly more precise by specifying what 'details' include.

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?

Given the lack of output schema, the description provides a hint about the return content ('including its layout'), but does not fully explain what details are included. With annotations covering safety, the description is adequate but leaves some ambiguity about the response structure.

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?

The schema has 100% coverage for the single required parameter 'sys_id' described as 'Page sys_id'. The description does not add further meaning or context about the parameter, so it meets the baseline for a fully documented schema without extra value.

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 identifies the tool as retrieving details of a specific Service Portal page, using the verb 'Get' and specifying the resource and scope ('including its layout'). This distinguishes it clearly from siblings like list_portal_pages (listing) or get_portal (portal-level details).

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 guidance is provided on when to use this tool versus alternatives like list_portal_pages or get_portal. The description lacks explicit context for when/not-to-use, and does not mention any prerequisites or alternative tools.

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