vram_usage

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

No annotations provided; description carries full burden. Clearly states it reads VRAM and optionally flags over-budget models. Does not mention side effects, permissions, or rate limits, but for a read operation the behavior is adequately disclosed. The [READ] tag helps.

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?

Extremely concise: one sentence plus two arg lines. Every sentence adds value. Front-loaded with '[READ]' for quick scanning.

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?

No output schema, so description should explain return values. Implies output includes total VRAM and flagged models, but lacks format details. Does not mention edge cases like no models loaded or invalid target. Adequate for a simple query but not fully complete.

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 0%, so description must compensate. Describes budget_bytes as 'Optional VRAM budget; models over it are flagged' and target as 'Ollama target name from config; omit for the default.' Adds meaning beyond schema types but minimal detail.

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?

Starts with '[READ]' clearly indicating read operation. States specific verb+resource: 'Total VRAM used by loaded models; flag over-budget.' Distinguishes from siblings like running_models (lists models) and server_status (general status) by focusing on VRAM usage and budgeting.

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 explicit when-to-use or alternatives. The budget_bytes parameter hints at context (monitoring VRAM budgets), but no guidance on when to use this over other monitoring tools like server_status or running_models.

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