query_local_ai_service

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: not what gets queried, whether the call mutates state, auth requirements, or rate limits. The only context is the 'Ollama-compatible' protocol hint.

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?

One short sentence is technically compact, but this is under-specification rather than conciseness. The line fails to earn its place by omitting any actionable detail.

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?

An output schema exists so return values needn't be explained, but the definition is far too thin for a 3-param tool with zero annotation and schema-description coverage. The agent has no basis for constructing a correct call.

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% for 3 parameters, and the description compensates for none of it. It says nothing about the required 'endpoint' format, the meaning of 'method' or its GET default, or the shape of 'data'.

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?

'Query Local AI (Ollama-compatible) service' essentially restates the tool name. The 'Ollama-compatible' qualifier adds a small hint about the protocol, but the description offers no distinction from the many sibling query tools (query_vibe_proxy, query_nexus, chat_with_local_model), so an agent cannot tell them apart.

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 when-to-use guidance and no alternatives named, despite a crowded sibling set of query/chat tools. The agent gets no signal about when this is preferable to chat_with_local_model or query_vibe_proxy.

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