get_notification

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

Annotations already indicate readOnlyHint=true, so the tool is known to be a read operation. The description adds context by specifying that 'template and conditions' are included in the returned details, which provides some behavioral clarity. However, it does not disclose other traits like permissions, rate limits, or the exact response structure.

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 with no redundant words. It efficiently conveys the tool's purpose and key return contents.

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 simple getter with one parameter and good schema/annotations, the description is nearly complete. It specifies that full details including template and conditions are returned. Minor gap: it doesn't clarify whether 'full details' includes all fields or just those highlighted, but this is not critical given the annotations and simple scope.

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 input schema covers the only parameter (sys_id_or_name) with a clear description: 'Notification sys_id or name'. The tool description adds little beyond the schema, but since schema coverage is 100%, the baseline of 3 is appropriate. No additional parameter meaning is provided.

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's function: 'Get full details of an email notification definition including template and conditions'. It uses a specific verb ('Get'), identifies the resource ('email notification definition'), and lists included components, distinguishing it from sibling tools like list_notifications, create_notification, and update_notification.

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 usage for retrieving a single notification's details by sys_id or name, but provides no explicit guidance on when to use this tool versus alternatives such as list_notifications. There is no mention of exclusion criteria or preferred scenarios.

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