Fetch Houdini doc

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety and side-effect expectations are covered. The description adds little beyond that, such as what happens if the id is missing or whether the result includes full content, though it does clarify the item comes from search results.

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 single sentence is compact and front-loads the key operation and source of the id. 'OpenAI-compatible fetch' is somewhat vague and could be trimmed, but the description is not bloated.

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 one-parameter read tool with annotations covering safety and an output schema covering return values, the description supplies the essential context: it fetches a doc item by id obtained from search. Minor gaps like error behavior are acceptable given the tool's simplicity.

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 0%, so the description must carry parameter meaning. It does explain that the id refers to a documentation item returned by search, which is useful context beyond the raw schema, but it does not specify id format, validity rules, or failure behavior.

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 states a specific verb (fetch) and resource (documentation item) scoped by id, and it identifies the source of that id as search results. It is clear enough to distinguish this from siblings like search or get_skill, though 'OpenAI-compatible fetch' is slightly jargon-heavy.

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 phrase 'from search results' gives clear implied usage: call search first, then use this tool with a returned id. It does not explicitly name the search sibling or describe when not to use this tool, but the context is strong for a simple fetch operation.

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