post_show_model

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

With no annotations, the description carries the full burden. It explains the API endpoint, return format (JSON with specific fields), and error behavior ('fails, returns error information'). It does not cover authentication or rate limits but is adequate for a read-only operation.

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 well-structured with Args and Returns sections. It is front-loaded with the purpose. However, the first sentence slightly restates the title ('Show detailed information about a model'). It is concise but not overly terse.

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?

Given one parameter, no annotations, and the presence of an output schema (implied by return description), the description covers the return format well. It lacks prerequisites (e.g., Ollama must be running) but is largely complete for a simple retrieval tool.

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?

The schema has 0% description coverage, so the description must add value. It explains that the 'model' parameter is a model name with examples ('llama2', 'mistral'), but lacks deeper semantics like format constraints, validation, or list of valid values.

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 the verb ('retrieves detailed information') and the resource ('model'), and specifically mentions the API endpoint '/api/show'. It distinguishes from sibling tools like get_ollama_list (which lists models) and simple_chat (which generates responses).

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 implies usage when needing detailed model info but provides no explicit guidance on when to use vs. alternatives like get_ollama_list or when not to use. Sibling tool names suggest alternatives, but no comparisons or exclusions are mentioned.

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