Skip to main content
Glama

Describe a task

describe
DestructiveIdempotent

Replace an open Tisty task's full written details after reading the current version; retain valid content and record new findings in a note.

Instructions

Write the description of an open task. It replaces the old one whole: read first and keep what holds; what you learnt goes in note.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task": "<task>",
      "body": "<body>"
    },
    "name": "describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesWhat the task is, in the Tisty language
taskYesThe task id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the replacement semantics are partly pre-signalled. The description still earns credit by making the wholesale replacement explicit ('It replaces the old one whole') and warning to read first so prior content is not lost, which is the key operational risk. It does not describe the result of the call or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the destructive behaviour front-loaded and no filler. The phrasing 'keep what holds' is idiomatic and slightly opaque, costing a little clarity against its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive write with no output schema, the definition covers what to do before calling, what gets overwritten, and where non-description content belongs. Missing only an explicit statement of the expected response or whether the task must be in a particular state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, making 3 the baseline. The description adds the crucial nuance that `body` overwrites rather than merges, but it also references `note`, which is not a parameter of this tool and could momentarily confuse which field receives what.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Write the description of an open task') and implicitly separates this from the sibling `note` by saying learnings belong there instead. It is clear what the tool does, though it never explicitly contrasts itself with other write tools such as edit_doc or append_doc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete prerequisite workflow: read the task first and preserve what still holds, and routes ancillary learnings to `note`. There is no explicit statement of when not to use this tool, so it stops short of full when/when-not guidance.

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