search_comfyui_support

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

The description states 'Read-only, no storage,' which reinforces the readOnlyHint annotation and adds the small extra context that no storage is used. This is useful, but the annotation already covers the core safety trait, so the description only modestly adds beyond the structured data. No rate limits, pagination, or return format details are disclosed.

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 two concise sentences with no filler. The main action and object are front-loaded, and the read-only/no-storage behavior is stated in a compact second sentence. Every word earns its place.

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 simple search tool with four parameters, an output schema absent, and clear defaults/enums on the schema side, the description gives enough context to select and invoke it. It identifies the resource, topic, and safety profile; the only missing piece is a more explicit description of how sort/time values affect results, but those are still inferable from the schema.

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 description coverage is only 25%, and the description does not explain the 'sort', 'time', or 'limit' parameters; only 'query' is partially reflected via the phrase 'user-requested troubleshooting discussions.' The schema itself only documents 'query', leaving the other three parameters under-specified for an agent, and the description fails to compensate.

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 names a specific verb and resource: 'Search public r/comfyui posts' and defines the scope as 'user-requested troubleshooting discussions.' It is clearly a search tool for a particular community and topic, which is enough to distinguish it even though no sibling tools are listed.

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 makes the intended use clear: finding troubleshooting discussions in r/comfyui that match user-requested issues. It does not explicitly state when not to use it or list alternatives, but because there are no sibling tools provided, the clear context is sufficient for a correct call.

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