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

Beyond readOnlyHint=true, the description discloses the two behaviors that actually matter here: only PUBLISHED companies are visible in public view while owners can see their own company in any status, and a miss returns found=false. It does not discuss authentication requirements or the shape of the returned company object, which is the main remaining gap.

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?

Compact and front-loaded with the operation, then the visibility rule, then the not-found contract. The usage sentence and the resource URI would read better before the behavioral clauses, but nothing is redundant.

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 single-parameter read tool with no output schema, the description covers purpose, visibility scoping, and the negative-result case, and points to a related resource URI. The one thing an agent cannot infer is what fields the homepage payload contains, which keeps this from a 5.

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 the schema already documents the slug including the /c/<slug> URL form. The description only restates that lookup is by slug, adding no format or resolution detail beyond the schema, so 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: fetch a one-person company homepage by slug. The parenthetical about public view vs. owner view implicitly separates it from get_my_company and list_companies, though no sibling is named explicitly.

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 a concrete triggering scenario ('用户想看某家一人公司在做什么') plus the visibility condition that determines what comes back. It stops short of naming alternatives such as get_my_company for the caller's own company or list_companies for browsing, so routing is left partly to inference.

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