Torch Info

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

No annotations are provided, and the description gives no side effects, access constraints, output shape. For an unannotated GET-like tool, the description's short 'Get torch/GPU info' is its own burden. It does not add behavioral context beyond the fact that it is a GET request.

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?

Single sentence containing endpoint and method. Very tight 16 words, one line, no wasted content, exactly the needed information.

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?

Complete for this simple unparameterized info retrieval tool: has endpoint, resource, verb. Without output schema is okay, but return types or any notes are not. Given the simplicity of the tool and the richer sibling namespace, 4 is appropriate.

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?

Tool has 0 parameters and the input schema consists of an empty properties object, so parameter documentation is trivially complete. There is nothing for the description to add.

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?

Description states a specific action 'Get torch/GPU info' and identifies the exact endpoint (GET /sdapi/v1/torch). This distinguishes it clearly from a generic 'info' tool, though it does not explicitly name alternative sibling tools.

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 guidance on when to use this tool versus alternatives, no exclusions or prerequisites stated. The endpoint is mentioned but no when/when-not to use; only that it fetches info.

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