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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that — no pagination behavior, filtering behavior, or response characteristics for a list endpoint.

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?

Extremely short but not concise in a useful way: the same endpoint string appears twice, and the operation ID hash consumes space without informing an agent. Under-specification rather than economy.

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 nested-schema list operation with no output schema and no parameter documentation, the description should carry the burden; it only gestures at describe_operation. An agent cannot determine what is returned, how to filter, or what query accepts.

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 0% with two nested object parameters (query and params) whose properties are entirely undocumented, and the description supplies no parameter meaning, format, or examples to compensate. With a nested, opaque schema and zero coverage, this is a critical gap.

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 is essentially the HTTP method and path repeated verbatim ('GET /api/inventory/assignments' twice) plus an operation ID hash, which is a tautological restatement of the tool name/title. It never says what an 'assignment' is or how this differs from sibling inventory tools like get_inventory_items or get_inventory_locations.

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?

No when-to-use, when-not-to-use, or alternative routing is given. The only actionable hint is that describe_operation provides native request schemas, which is a lookup pointer rather than usage guidance.

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