get_content

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

Describes behavioral traits: searches collections first then categories, aggregates and deduplicates, pattern filtering, and force flag behavior. No annotations provided, so description carries full burden and does so well.

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?

Well-structured with clear sections and bullet points. Every sentence adds value, no redundancy. Appropriate length for complexity.

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?

Covers main purpose, search order, parameter behaviors. Does not mention output schema (present externally) or error cases. For a read tool, fairly complete.

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?

Schema coverage is 100%, but description adds value by explaining context: pattern overrides defaults, force returns full or reference content. Goes beyond repeating schema descriptions.

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?

Clearly states the tool retrieves content from collections and categories. Describes search order and deduplication, distinguishing it from sibling tools like category_content or export_content.

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?

Explains search order but does not explicitly state when to use this tool vs alternatives. Lacks guidance on when not to use it or which sibling to prefer for specific needs.

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