Jesse MCP Server

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

With no annotations provided, the description carries the full burden. It discloses the external service dependency (ntfy.sh) and return structure (status and timestamp), but omits critical behavioral traits like rate limits, authentication requirements, failure modes, or network timeout behavior for the external API call.

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?

Uses a structured docstring format (Args/Returns) that efficiently organizes information. All four sentences earn their place. The format is slightly verbose but maximally clear, with no redundant or tautological statements.

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 presence of an output schema (per context signals), the description appropriately provides only a high-level summary of returns ('status and timestamp') rather than duplicating schema details. All parameters are documented despite zero schema coverage, making this complete for a simple 3-parameter external API wrapper.

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?

Despite 0% schema description coverage, the Args section comprehensively documents all 3 parameters. It adds crucial semantic meaning beyond the schema: message content purpose, valid priority enum values (default, low, high, urgent), and the comma-separated format for tags. This fully compensates for the schema's lack of descriptions.

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 explicitly states 'Send a notification alert via ntfy.sh' - providing a specific verb (Send), resource (notification alert), and external service context (ntfy.sh). It clearly distinguishes itself from the 60+ sibling trading/backtesting tools by being the sole alerting utility.

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?

While there are no explicit 'when to use' instructions or alternatives listed, the tool's purpose is clear from context among trading-focused siblings. However, it lacks guidance on when to prefer this over other potential alerting mechanisms or prerequisites like ntfy.sh topic configuration.

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