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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered. The description adds non-obvious context beyond that: the upstream API validates its query/body contract, callers must not invent fields, and provider record text is untrusted data rather than instructions — a meaningful prompt-injection warning.

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?

Four short sentences with the purpose front-loaded and no filler. The doc-pointer and untrusted-data sentences are compact and each carries a distinct point, though the doc references are slightly list-like rather than integrated.

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?

An output schema exists, so return values need not be described, and annotations handle the safety profile. Still missing for a 1-param discovery tool: what an endpointId is and how to obtain a valid one, which is the single thing an agent must get right to call it.

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 0% and the single parameter endpointId is undocumented in both schema and description. The line 'Use organization IDs returned by reads' gestures at value provenance but is ambiguous — it is unclear whether endpointId is an organization ID, an operation identifier, or something else derived from that ID.

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 opening sentence gives a specific verb and object ('Get the HTTP operation and required path parameters'), and the title pins it to an organization API operation, so an agent can tell this is a schema/contract lookup rather than a data read. It does not name the sibling it contrasts with (e.g. system_read vs system_operation_status), so differentiation is only implicit.

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?

'Use organization IDs returned by reads' implies a read-then-describe workflow, and the documentation pointers (/mcp, smartshifts://policy) give an escalation path. However, there is no explicit statement of when to call this instead of system_read, system_inventory, or system_operation_status, and no when-not guidance.

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