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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds real behavioral context beyond them: full terms text is only fetched with includeTermsBody (capped at ~20k chars), currentTerms.bodyLength indicates body presence, myMembership.id is a membershipId not a userId, and application answer raw text is deliberately not surfaced through the Agent.

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?

Front-loads what the tool reads before the conditional/workflow notes, and every clause carries information with no filler. However the dense semicolon-run-on packaging makes it harder to scan than a cleanly segmented description.

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?

With no output schema, the description carries the return-value burden and does so reasonably: it names the returned facets, explains the terms-summary vs full-body distinction, and clarifies the identity of myMembership.id. Some nuances of the return shape and the anonymous-public-org behavior remain only lightly specified.

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%, so the schema already fully documents organizationId and includeTermsBody (including the 20k cap and default false). The description largely reinforces the same includeTermsBody semantics and adds output-shape notes rather than new parameter meaning, 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 (读/read) applied to a specific resource (组织/organization), then enumerates exactly what fields it returns: identity, visibility, membership policy, agreement summary, title, and the caller's own membership/application state. This is clearly distinguishable from siblings like create_organization, update_organization, or discover_organizations.

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 explicit conditions: use activity_members_only to check eligibility, pass includeTermsBody=true only when reading the terms aloud for confirmation, and do not repeat the application while it is PENDING. It also sequences the follow-up tools (apply_to_organization then submit_signup), though it stops short of a full when-not-to-use statement versus every alternative.

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