spoolman_get_spool

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

With no annotations, the description carries the full burden. It discloses that the tool returns remaining weight and usage stats, which is useful, but it does not mention error behavior (e.g., unknown ID) or any access prerequisites. The simple read nature is adequately conveyed, but some transparency gaps remain.

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 a single, front-loaded sentence that clearly states the operation and key output details without any wasted words or redundancy.

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?

The description covers the primary return content ('remaining weight and usage stats') and the tool is simple with one parameter. However, no output schema exists, and the description does not specify response structure or error cases, leaving minor gaps given the lack of structured return documentation.

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 description for the single parameter 'id' is 'The spool ID' with an exclusiveMinimum, providing 100% coverage. The tool description adds no extra semantic meaning beyond the schema, so the baseline of 3 applies.

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 uses the specific verb 'Get' with the resource 'a single spool by its ID', clearly distinguishing it from list operations like list_spools. Mentioning 'remaining weight and usage stats' further clarifies what data is returned, making the purpose unambiguous.

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 a spool ID is known and a single spool's details are needed. However, it does not explicitly state when to prefer this over alternatives like list_spools or provide exclusion criteria, so guidance is only implied.

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