sendAppPushTaskReminder

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

No annotations are provided, so the description must convey behavioral traits. It does not mention side effects, required permissions, or success/error behavior. The description only states the action without any transparency about what happens technically or operationally.

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, succinct sentence with no unnecessary words. It is appropriately concise for a simple tool, though it could benefit from slightly more context without sacrificing brevity.

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?

Given the 2 parameters, no output schema, and no annotations, the description is too sparse. It omits important context such as the return format (success indicator?), prerequisites (e.g., lead must have app installed), and how the task reminder is triggered. Incomplete for fully guided usage.

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% with basic descriptions ('Lead ID', 'Task ID'). The tool description adds no additional meaning beyond the schema, so it meets the baseline of 3 for high coverage but does not enhance parameter understanding.

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 sends an app push task reminder notification, using a specific verb and resource. It distinguishes from sibling notification tools like sendEmail or sendSms by specifying 'app push' channel. However, it lacks detail about the recipient (e.g., lead or agent) and the exact context of 'task reminder'.

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?

There is no guidance on when to use this tool vs alternative notification methods (sendEmail, sendSms, sendOpportunityNotification). No context about prerequisites or scenarios where this is appropriate.

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