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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds substantial context on top: which fields a package exposes (manifest, owner, creator, creator faction), the freight-contract shipment block contents, faction intel inclusion, and the not_found failure case. It stops short of describing rate limits or response shape in full, so it is strong but not exhaustive.

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?

Content-dense with no filler and the core purpose is front-loaded before the qualifiers. However, it is delivered as one long parenthetical blob with nested parentheses ('(not_found)', freight block lists), which makes the structure harder to scan than clean sentence separation would.

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 carries the return-value burden and largely discharges it by explaining what packages, systems, and POIs report, plus conditional visibility and the not_found case. Base detail handling is covered via the docking requirement, leaving only minor gaps in the broader response envelope.

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 description coverage is 100% and both required parameters (id, session_id) are documented in the schema. The description restates the same ID-type list the schema already carries and adds no syntax, format, or validation detail beyond it, so the 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 ('Inspect') plus a precise enumeration of the accepted resource types (package, item, module, ship class, system, POI, docked base) keyed by ID. It also distinguishes itself from the sibling catalog tool by routing skills/recipes/facilities there, so an agent can tell it apart from get_poi, get_system, get_base, or catalog.

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?

Gives explicit when-to-use conditions: packages resolve only when held by you/your faction or in a pending direct trade; POIs must be in your current system; a hidden uncharted POI returns not_found; full base details require docking. It also names the alternative ('Look up skills, recipes, and facilities with catalog'), leaving little to inference.

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