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

Annotations already cover readOnlyHint and idempotentHint, so the safety profile is established. The description adds meaningful context beyond that: it lists the specific live data returned (coordinates, condition, movement endpoints, completion tick) and states the authorization rule that any faction member may query it, which the annotations do not convey.

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?

One sentence in parenthetical form front-loads the action and resource, then enumerates the returned state and access rule. It is efficient, though the parenthetical wrapping is slightly awkward and the field list is dense.

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?

There is no output schema, so the description must carry the return-value burden. It partially does so by naming the fields (live system, coordinates, condition, archetype, movement endpoints, completion tick), but it does not specify return format, pagination, or failure behavior (e.g., what happens if the faction has no mobile base).

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% and there is only one parameter (session_id), whose description is already provided in the schema. With a single fully-documented parameter, the description need not add syntax; the baseline is met and no compensation is required.

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?

Specific verb (Inspect) plus specific resource (your faction's mobile base) and an explicit enumeration of returned fields. It clearly differs from siblings like build_base, move_faction_mobile_base, or decommission_faction_mobile_base.

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 parenthetical '(Any faction member may query it.)' gives an access condition, and the sibling set implies this is the read counterpart to move/jump/cancel tools. But there is no explicit when-to-use or when-to-use-alternatives routing like 'use get_base for regular bases' or 'use move_faction_mobile_base to change position'.

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