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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral value beyond them by disclosing exactly what data the profile contains, including that funding rounds come 'with sources' – useful for judging output trustworthiness.

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?

The content is front-loaded and each clause lists real return fields, but the entire description is duplicated in Chinese and English, so roughly half the text repeats itself rather than adding information.

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 simple two-parameter read tool with full schema coverage and annotations carrying the safety profile, the description covers purpose, lookup key and returned fields adequately. Without an output schema, naming the response contents is a reasonable substitute, though freshness or auth expectations are unstated.

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 both parameters (ref, lang with default zh) are already documented in the schema. The description restates that lookup works 'by name or slug' but adds no format, alias-resolution, or language-override detail beyond the schema.

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 ('Get the public profile of one organization') and enumerates the payload (intro, sector, HQ, total funding, funding rounds with sources). The 'one organization' scope implicitly contrasts with the plural search_organizations sibling, but it never names that sibling explicitly, so it stops short of a 5.

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?

Usage is only implied: the agent infers this is the tool to call when it already has a name/alias/slug for a single org. There is no statement of when to prefer it over search_organizations or get_person_profile, and no exclusions or prerequisites given.

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