get_unit_system

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

No annotations are provided, so the description carries the full behavioral burden. It does not explicitly state that this is a read-only operation with no side effects, nor does it describe what happens if no unit system preference is set or whether other profile data is included. The verb 'Get' hints at read-only behavior, but little else is disclosed.

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 sentence with no filler. The key action and object are front-loaded, and the source is stated concisely.

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?

For a zero-parameter getter, this description is complete: it identifies what is returned and where it comes from, and the presence of an output schema covers the return-value details. No additional field-level or usage detail is necessary.

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 tool has zero parameters and the input schema is fully covered, so there are no parameter semantics to clarify. The description still adds value by naming the profile source and the specific unit-system preference being retrieved.

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 states a specific verb ('Get'), a focused resource ('preferred unit system'), and a source ('profile'). It clearly distinguishes this from broader sibling tools like get_user_profile or get_userprofile_settings because it names the exact property being retrieved.

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 intended use is implied: call this when you need the user's preferred unit system from their profile. However, it does not explicitly mention when not to use it or how it compares to sibling profile-related getters, so the guidance is mostly implicit.

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