llmconveyors-mcp

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

With no annotations provided, description carries full disclosure burden and succeeds well: states 'irreversible' nature, declares auth requirement 'sessions:write', and details cascade scope (generations, artifacts, logs). Minor gap: no mention of error behavior (e.g., not found) or rate limits.

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?

Perfectly structured four-sentence flow: action definition → destruction warning → use case → prerequisites/auth. Zero waste; every clause delivers unique operational intelligence.

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?

Comprehensive for a destructive tool without output schema: covers scope, risks, authorization, and workflow prerequisites. Could enhance with error condition description (e.g., session not found), but adequately complete given the simple input surface.

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 has 100% description coverage ('Session ID'), so baseline 3 applies. Description implies the target through context but doesn't add syntax examples or validation rules beyond the schema.

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: 'Permanently delete a session and all its generations, artifacts, and logs' provides exact verb, resource, and scope. Distinguishes from sibling content-delete tools by emphasizing cascading deletion of session children.

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?

Explicit guidance throughout: 'Use this to clean up completed or unwanted sessions' defines when to use; 'Use session-list to find sessions, and session-hydrate to review contents before deleting' names specific alternatives for the discovery phase, creating clear workflow sequencing.

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