Get Model Scale

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

No annotations are provided, so the description must disclose behavioral traits. It implies a read-only operation ('Get'), but does not explicitly state non-destructive behavior or any side effects. However, the context of querying before changes adds useful transparency, making it mostly adequate.

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 front-loaded with the purpose and followed by usage guidelines in two succinct sentences. Every sentence adds value without 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?

While no output schema is provided, the description mentions scale factors for x, y, z, giving a basic idea of the return format. For a simple getter with no parameters, this is mostly complete, though specifying the exact structure (e.g., object) would be ideal.

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 input schema has no parameters and achieves 100% coverage, so baseline is 4. The description adds no parameter information (unnecessary), but correctly focuses on usage context.

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 tool gets the current model scale in each dimension (x, y, z) as scale factors. This is specific with a verb and resource, distinguishing it from siblings like scale_model.

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 explicitly advises querying before relative scale changes for accuracy, and notes that for absolute changes, recently queried state may be used if no manual interactions occurred. This provides clear when-to-use guidance and an alternative approach.

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