Start monitoring an MCP server on the caller's Toolpin account, so they are emailed when it changes or stops answering. Needs an API key. Says so plainly if the account is already at its plan limit rather than failing.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses it requires an API key and handles plan-limit errors gracefully. It also states the effect (emails on changes/stops). However, it doesn't mention whether this creates a persistent watch, is idempotent, or is reversible. Some behavioral context is provided but not comprehensive.
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 concise sentences, front-loaded with purpose, then requirements and edge-case behavior. No wasted words.
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 single-parameter tool with no annotations or output schema, the description covers purpose, a requirement, and one error behavior. It lacks return-value information and any detail on how the name is validated, but the tool is simple. It's adequate but not rich.
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 0%, and the description does not explicitly explain the 'name' parameter. It implies it identifies the server to monitor but never directly states that. The API key requirement is mentioned but is not a parameter. The description fails to fully compensate for the lack of schema documentation.
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 ('Start monitoring') and resource ('MCP server on the caller's Toolpin account'), and distinguishes from sibling get/search tools by describing a mutating action with a distinct outcome (email notifications).
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?
No guidance on when to use this tool versus the siblings (get_server, get_server_changes, etc.). The description implies a monitoring use case but doesn't explicitly contrast it with alternatives or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.