tsort

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

The description states 'Read-only, no side effects,' aligning with annotations (readOnlyHint=true). It also describes behavior beyond annotations: 'detecting cycles... reports cycles with specific node information on error.' No contradiction.

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?

The description is concise with six sentences, each adding unique information (purpose, behavior, usage, disambiguation). It is front-loaded but could be more structured; nonetheless, it avoids unnecessary words.

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?

Despite no output schema, the description explains the return format ('Returns JSON with the sorted order') and error behavior. The tool is straightforward: parameter roles are clear from schema, and the description covers critical context for correct use.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds context about the expected input format ('whitespace-separated dependency pairs'), which is not in the schema, enhancing parameter meaning.

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 uses a specific verb 'Perform topological sort' and clearly identifies the resource ('whitespace-separated dependency pairs'). It explicitly distinguishes from sibling 'sort' by stating 'Not for lexical sorting — use "sort" for alphabetical or numerical ordering.'

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?

The description provides explicit when-to-use ('Use for dependency resolution and build-order calculation') and when-not-to-use ('Not for lexical sorting... use "sort"'), including a direct reference to the alternative 'sort'.

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