llmconveyors-mcp

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

With zero annotations provided, the description carries the full disclosure burden admirably. It reveals rate limiting ('5 per hour'), required authorization scope ('webhook:write'), destructive traits ('immediately invalidating the old secret'), and downstream impact ('All existing webhook receivers must be updated').

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 sentences total, each earning its place: core action, breaking-change warning, rate limit constraint, and auth/alternative prerequisite. Information is front-loaded with the destructive action, followed by critical operational warnings. No redundancy or tautology.

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 lack of annotations and output schema, the description achieves completeness by conveying the mutation semantics, side effects, and operational limits. It implies the return value ('generating a new one' combined with the instruction to update receivers with it) sufficiently for agent invocation without explicit schema documentation.

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?

The input schema contains zero parameters (empty properties object), establishing a baseline score of 4. The description correctly omits parameter discussion as there are none to document, adhering to the rule that zero parameters defaults to baseline 4.

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 opens with a precise verb ('Rotate') and resource ('webhook signing secret'), immediately clarifying the tool's function. It distinguishes itself from sibling 'webhook-secret-get' by explicitly naming it as the prerequisite for retrieval, clearly separating read vs. write intent.

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 sequencing guidance ('Use webhook-secret-get to retrieve the current secret before rotating'), establishes prerequisites (receivers must be updated), and warns of failure modes ('they will reject incoming payloads'). This fully defines when and how to use the tool versus its alternative.

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