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

Adds real context beyond readOnlyHint=true: the return contains obfuscated company ids consumed by other tools, and the underlying endpoint is POST /v1/companies:list — useful because a POST verb might otherwise suggest a mutation. It does not mention pagination defaults or result ordering.

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?

Three short sentences, no filler, and the 'call first' prerequisite is front-loaded before the API path.

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 two-param read tool with no output schema, it covers purpose, prerequisite ordering, and the key return value (company ids). The shape of the returned company objects and paging behavior are left implicit, a minor gap.

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 parameters (page_size, page_token) are already documented in the schema; the description adds nothing about paging. 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 and resource with scope: 'List the companies the API key can access.' That clearly separates it from the singular moego_get_company, though it never contrasts itself with the close sibling moego_list_businesses.

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?

'Call first: it returns the obfuscated company ids that every other tool needs' gives explicit ordering plus the dependency reason, so an agent knows both when to call it and why it must precede other tools.

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