get_unit

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds no additional behavioral context such as error behavior, authentication, or return format. While there is no contradiction, the description contributes nothing beyond the name.

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?

A single four-word sentence is maximally concise and front-loaded. Every word earns its place, with no fluff or repetition.

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?

Given the one-parameter schema and rich annotations, the description is adequate but terse. It doesn't state what a 'unit' is or what is returned, but the name and schema cover the essentials. For a simple get-by-ID tool, this may be sufficient; however, no output schema means a bit more context would help.

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 covers 100% of the parameter with a clear description ('the id of the unit'), so the description does not need to add parameter details. Baseline 3 is appropriate; 'Fetch a unit' adds no extra semantic meaning.

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 'Fetch a unit' uses a specific verb and resource, clearly indicating a retrieval operation for a single unit. It distinguishes itself from sibling tools like list_units (plural collection) and search_units (query-based) by implying direct fetch by ID.

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 provides no explicit guidance on when to use this tool versus list_units or search_units, nor does it mention exclusions. Usage is only implied by the name and the required unit_id parameter.

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