MCP Outline Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool does (finds backlinks) and what it returns (formatted string listing documents), but doesn't mention important behavioral aspects like whether it requires specific permissions, how it handles large result sets, or if there are rate limits. The description adds basic context but leaves gaps for a read operation.

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 well-structured and appropriately sized with clear sections: purpose statement, usage guidelines, parameters, and returns. Every sentence earns its place by providing distinct value, and the information is front-loaded with the core purpose first.

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 single-parameter read operation with no annotations or output schema, the description provides good coverage of purpose, usage, and basic parameter semantics. However, it lacks details about the return format beyond 'formatted string' and doesn't address potential limitations or error conditions, leaving some gaps in completeness.

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 0% schema description coverage and only one parameter, the description compensates by clearly explaining the document_id parameter's purpose ('The document ID to find backlinks for'). This adds meaningful semantics beyond what the bare schema provides, though it doesn't specify format requirements or validation rules.

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 clearly states the tool's purpose with a specific verb ('Finds') and resource ('all documents that link to a specific document'), distinguishing it from siblings like search_documents or list_collections. It precisely defines the scope as discovering backlinks rather than general document operations.

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 explicitly provides four bullet points detailing when to use this tool, including discovering references, identifying dependencies, finding related documents, and understanding relationships. This gives clear context for when this tool is appropriate versus alternatives like search_documents or get_collection_structure.

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