llmconveyors-mcp

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

No annotations provided, so description carries full disclosure burden. Successfully communicates mutability ('Append', 'Creates') and authorization requirement ('sessions:write'). Could improve by mentioning idempotency behavior or error conditions (e.g., invalid session ID), but covers essential safety profile.

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 with zero waste: action definition, mechanism, use case, and requirements/alternatives. Front-loaded with critical verb 'Append'. No redundant phrases despite Compound sentence structure.

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?

Complete for a 4-parameter write operation without output schema. Covers auth scope, sibling differentiation, and parameter intent (via audit trail explanation). Absence of output schema is accepted per rules; description adequately explains side effects without return value 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?

Schema has 100% description coverage (baseline 3). Description adds semantic context by mapping parameters to use cases: 'tracking conversation history, tool usage, or status updates' clarifies intent of 'role' parameter and 'content'/'payload' distinction for audit trails, exceeding baseline 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?

Opens with specific verb 'Append' and clear resource 'log entry to an existing session'. Explicitly distinguishes from sibling 'session-hydrate' (for reading back history) and enumerates use cases (conversation history, tool usage, status updates) that map to the role enum values.

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 alternative: 'Use session-hydrate to read back the full log history' establishes when NOT to use this tool. States prerequisite 'Requires scope: sessions:write' and clarifies purpose with 'maintain an audit trail'.

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