outline_get_collection

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 but fails to state whether this is read-only, what format the returned information takes, or whether it includes nested documents. The term 'information' is too generic to convey actual behavior.

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 a single, efficient sentence with no wasted words. However, given the lack of annotations and output schema, extreme brevity becomes a liability rather than a virtue—additional sentences are needed to explain return values and usage context.

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?

Without an output schema or annotations, the description should explain what 'information' is returned and behavioral traits like permissions or error states. As a simple single-parameter retrieval tool, it requires minimal complexity, but the complete omission of return value description creates a significant gap.

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?

The input schema has 100% description coverage ('The ID of the collection to retrieve'), so the baseline score is 3. The description adds no additional semantic context about the ID format or validation rules, but the schema adequately documents the single parameter.

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 identifies the verb ('Get') and resource ('collection'), but uses vague phrasing ('information') that doesn't specify what data is returned—metadata, contents, or settings. It minimally distinguishes from outline_list_collections by specifying 'specific collection,' but doesn't clarify how it differs from document-related siblings.

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 is provided on when to use this tool versus outline_list_collections (which presumably lists all collections) or when to prefer outline_get_document. The description lacks prerequisites, error conditions, or workflow context despite the presence of closely related sibling tools.

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