llmconveyors-mcp

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

With no annotations provided, the description carries the full behavioral burden and succeeds well: explicitly declares 'Read-only, no side effects' covering safety profile, states the required auth scope ('webhook:read'), and implies sensitivity by referencing the rotation sibling. Could improve by mentioning return format or caching behavior, but covers critical operational traits.

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?

Four tightly constructed sentences with zero redundancy. Front-loaded with the core action (Get...), followed by usage context, operational constraints, and sibling reference. Every clause adds distinct value regarding purpose, security, or selection logic.

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?

Fully appropriate for a zero-parameter read operation. Compensates adequately for missing annotations by declaring auth requirements and safety properties. No output schema exists, but the description clearly identifies what data is returned (the signing secret). Mentions the relevant sibling tool needed for the complete lifecycle management.

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?

Zero parameters present per schema and context signals. Per the baseline rule, this earns a 4. The description appropriately focuses on behavior and output value rather than inventing parameter documentation where none exists.

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?

Excellent specificity: identifies the exact resource (webhook signing secret), its purpose (verify webhook payloads), and platform context (LLM Conveyors). Clearly distinguishes from sibling `webhook-secret-rotate` by stating this retrieves the current secret while the other generates a new one.

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?

Provides explicit when-to-use context ('when setting up webhook receivers') and security purpose ('validate that incoming webhooks are authentic'). Names the exact alternative tool for rotation scenarios ('Use webhook-secret-rotate'), making selection between the two unambiguous.

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