conduyt_create_notification

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

No annotations are provided, so the description carries the full disclosure burden, yet it adds little: the 'web push' side effect is already stated more precisely in the push parameter ('default true'). Nothing is said about who may target whom (userId defaults to API key owner, but can you notify other users?), permissions, failure modes, or rate limits for a mutation that fires external pushes.

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?

Two short sentences with the core action front-loaded and no filler. Appropriate size for the amount of information conveyed.

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 7-parameter create tool with a nested metadata object and no output schema, the description says nothing about what is returned (a notification ID?) or what the metadata object should contain, and does not compensate for the missing annotations. It is minimally adequate but leaves meaningful gaps.

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 description coverage is 100%, with every property documented including defaults, char limits and the nested metadata object, so the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema.

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?

States a specific verb and resource ('Send an in-app notification to a team member'), which is unambiguous. However it never distinguishes itself from the sibling conduyt_list_notifications or explains how this relates to other messaging tools (send_sms, send_email), so sibling differentiation is absent.

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 usage context is implied by 'to a team member' — this is for notifying a colleague, not the API caller. But there is no explicit when-to-use/when-not, no mention of the sibling list_notifications for reading, and no guidance on choosing between push and non-push delivery.

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