edstem-mcp

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention whether the operation is reversible, what happens if the thread is already unpinned, or any side effects on thread ordering/visibility.

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?

While the three-word description is not verbose, it suffers from under-specification rather than genuine conciseness. Every sentence should earn its place, but this provides minimal value beyond the tool name itself.

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 mutation tool with no annotations and no output schema, the description is inadequate. It omits behavioral scope, error conditions, and relationship to the pinning system that would help an agent invoke this correctly.

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?

With 100% schema description coverage (thread_id is documented as 'Global thread ID'), the baseline is 3. The description adds no additional parameter context (e.g., where to find this ID, format constraints), so it meets but does not exceed the baseline.

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 'Unpin a thread' is tautological—it simply restates the tool name with spaces instead of underscores. It fails to specify what 'unpinning' means functionally (e.g., removing from top of list) and does not distinguish from the sibling 'pin_thread' tool.

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 provided on when to use this tool versus 'pin_thread' or other sibling tools. No mention of prerequisites (e.g., thread must be pinned first) or expected outcomes.

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