get_notifications

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While '取得します' (retrieves) implies a read operation, the description doesn't mention authentication requirements, rate limits, error conditions, or what format the notification settings are returned in. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient Japanese sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for what it communicates and is front-loaded with the core functionality.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'notification condition settings' include, what format they're returned in, whether there are authentication requirements, or how this differs from other notification-related tools. The agent would have significant gaps in understanding how to properly use this tool.

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% description coverage, so both parameters (app_id and preview) are already documented in the schema. The description doesn't add any additional parameter context beyond what the schema provides, such as explaining what 'notification condition settings' specifically include or how the preview parameter affects the retrieval.

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 action ('取得します' - retrieves/get) and resource ('kintoneアプリの通知条件設定' - Kintone app notification condition settings). It's specific about what is being retrieved, though it doesn't explicitly differentiate from sibling tools like 'get_per_record_notifications' or 'get_reminder_notifications' which also retrieve notification-related data.

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 provides no guidance on when to use this tool versus alternatives. There are several sibling tools that retrieve notification-related data (get_per_record_notifications, get_reminder_notifications), but the description doesn't help an agent understand when this specific notification settings retrieval is appropriate versus those other options.

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