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

readOnlyHint=true already declares the safety profile, so the description only needs to add context. It does add something useful: the explicit exclusion '不返回登录电话或密钥' clarifies privacy masking, and the field list implies the return shape despite no output schema. It still omits permission or membership prerequisites hinted at by the opaque first clause.

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?

Two sentences with no padding, but the first clause '登录/组织撮合员工' is front-loaded and confusing rather than informative. The substantive field list is not placed first, so the reader must decode the opening fragment before reaching useful content.

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 readOnlyHint and no output schema, the field enumeration partially substitutes for return-value documentation, and the exclusion note covers sensitive data. However, the meaning of organizationId and any required role or membership are left unstated, leaving real gaps for an agent to guess.

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 has one required parameter, organizationId, with 0% schema description coverage, and the description never mentions it or explains what form of identifier is expected. With low coverage the description must compensate, and it does not. Only the name of the parameter carries meaning here.

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 names a specific resource (茶馆经营配置) and enumerates the exact fields read: public intro, business phone, default seat price/capacity, cloud candidate range, and mini-program authorization status. The leading clause '登录/组织撮合员工' is ambiguous and reads more like an access note than a purpose statement, but the field list makes the read behavior identifiable. It does not distinguish itself from siblings like get_organization or update_organization_teahouse.

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?

There is no explicit when-to-use guidance and no mention of alternatives. It never states that update_organization_teahouse is the counterpart for modifying these settings, or under what conditions an agent should fetch this configuration at all. Usage is only inferable from the read verb.

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