send_organization_notification

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it only says 'send notification to organization'. It does not mention permission requirements, whether the message goes to all organization members, delivery guarantees, rate limits, or result/error behavior. The basic side effect is clear, but meaningful behavioral transparency is absent.

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 short sentence with no filler or redundancy. It is front-loaded and all content is relevant, though minimal.

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 state-changing tool with no annotations and no output schema, the description is quite thin. It omits target audience, expected return behavior, and usage context beyond the bare action. The parameter schema helps, but the overall description is not complete enough for confident invocation decisions.

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 coverage is 100%: message is clearly described as the notification content, and serviceName/serviceLogoUrl are optional with environment variable fallbacks. The description itself adds no parameter-level detail, but the schema already documents all parameters, so the baseline 3 applies.

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 Japanese description '組織に通知を送信する' clearly states the action (send notification) and target (organization), so the tool's purpose is easy to grasp. It does not explicitly contrast with send_workspace_notification or send_group_notification, but the org target does distinguish it among sibling tools. It adds little beyond the tool name, so it stops short of a 5.

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 instead of send_workspace_notification or send_group_notification. There are no conditions, exclusions, or alternative tool mentions. The agent must rely solely on the tool name to infer targeting semantics.

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