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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine domain semantics beyond that: the meaning of base_target, the 0-100 metric ranges, direction-of-good for each metric, and that values are not monetary.

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?

Front-loaded with the core action in the first sentence, followed by dense but relevant semantic clarifications. Every sentence carries meaning, though the parenthetical is somewhat crammed.

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?

With no output schema, the description usefully compensates by explaining the returned metrics' ranges and direction-of-good plus the base_target concept. For a single-param read tool this is close to complete, lacking only minor format notes.

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?

Schema coverage is 100% for the single required id parameter, so the schema fully documents the input. The description adds no syntax or format detail for id; its value is in interpreting the returned entity's fields rather than the parameter. Baseline 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?

States a specific verb (get), resource (infrastructure LoS target), and retrieval key (by ID), and its scope is clearly differentiated from the sibling list_infrastructure_los_targets which it names.

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?

Points the agent to list_infrastructure_los_targets when the criticality adjustment explanation is needed, giving a clear context for choosing between the two. It does not state explicit when-not-to-use conditions, but the routing context is concrete.

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