search_swift_content

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

No annotations are provided, so the description must fully disclose behavior. It mentions inclusion of premium content when Patreon is enabled but omits details on rate limits, authentication, read-only nature, pagination, or result limits, which are critical for an AI agent.

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?

Two sentences with no extraneous content. Purpose is front-loaded, and each sentence serves a distinct function (explaining scope and conditional inclusion).

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?

Tool has 2 parameters, no annotations, and no output schema. Description fails to specify return value format, pagination, result limits, or behavior when no sources are enabled. This leaves significant gaps for an agent to correctly invoke and interpret results.

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% (both parameters have descriptions). The description adds minimal value beyond the schema: it repeats the query usage hint and notes premium inclusion, but does not explain parameter formatting or constraints beyond what is in the schema.

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 it performs unified search across all enabled sources, including premium when Patreon is enabled. The verb 'search' and resource 'swift content' are specific, and it is distinct from sibling tools (enable_source, get_swift_pattern, list_content_sources).

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?

Provides explicit instruction to use for 'broad natural-language queries.' Does not state when not to use, but no conflicting sibling search tools exist, so exclusion is unnecessary.

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