list_notification_schema

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. However, the description adds no behavioral detail beyond the name—it doesn't explain what kind of schema is returned or how it can be used. With annotations present, the description should add context but does not.

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 extremely short—'Read Notification' plus an endpoint. While it is concise, it is under-specified and lacks structure. It does not front-load key information or provide a useful overview. It reads more like a placeholder than a helpful description.

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?

Although an output schema exists, the description doesn't explain what this tool returns or why an agent would use it. It's a schema-listing endpoint but the description doesn't clarify that it provides the JSON schema for notifications, nor does it mention any related use cases. The tool is incomplete in context.

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?

There are zero parameters, so the schema already covers everything. The description doesn't need to explain parameter details. Baseline for 0 params is 4, which is appropriate 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 says 'Read Notification' which is vague and does not clearly state that it retrieves the schema for notifications. It doesn't differentiate from siblings like list_notification which lists actual notifications. The endpoint is provided but not explained.

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 on when to use this tool versus alternatives. It doesn't mention that it's useful for inspecting notification schema before creation or updates, nor does it exclude any cases. Simply a read operation with no context.

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