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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely new behavior: a login is required, the lookup is unfiltered by status (ARCHIVED companies are returned), and the result is company=null when the user has none. The empty-result behavior is the important non-obvious trait and it is disclosed. Return shape beyond that is not described, but no output schema exists to compensate either.

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 clauses, verb-first, with the scope and null case up front and the mutation prerequisite last. Very dense; the telegraphic style (semicolon-separated fragments) is slightly clipped but nothing is wasted.

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 zero-parameter read tool with readOnlyHint and no output schema, the description covers the prerequisites (login), the result domain (any status, null when absent) and the workflow role (prerequisite for mutations). Only marginal gaps remain, such as what fields the company object carries beyond id/slug/status.

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?

The tool takes zero parameters, so the baseline of 4 applies; the description correctly implies the only implicit input is the authenticated caller's identity.

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 states a specific verb and resource: read the caller's own single company (本人唯一公司), in any status including ARCHIVED. That scope qualifier distinguishes it from the sibling get_company / list_companies without naming them, so an agent can infer the difference but is not explicitly routed.

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?

It gives a concrete usage rule: read the existing fields, id, slug and status before modifying, delisting, or deleting (i.e., before update_my_company / archive_my_company / delete_my_company). It does not explicitly say 'use get_company for companies that are not yours', so the alternative-routing is implied rather than stated.

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