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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the data is 'public' and enumerates the returned fields, but says nothing about behavior on unknown refs, result freshness, or empty responses.

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-loaded with the core action and field list, two short sentences. The cost is that the Chinese and English halves are near-identical in content, doubling length for i18n purposes 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?

With only two parameters, no output schema and annotations covering the safety profile, the description is largely sufficient; listing the three returned facets compensates for the absent output schema. It stops short of describing error behavior or how a slug is resolved.

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% and both parameters are documented in-schema (ref as name or svtr.ai slug, lang defaulting to zh). The description only restates the name/slug notion in Chinese and never mentions the lang parameter, so it adds no meaning beyond the schema. 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 the public profile of one founder/investor, and enumerates the returned facets (current roles, work experience, education). The 'person' framing implicitly separates it from the sibling get_organization_profile, but 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?

Usage is implied by the input hint (look up by name or slug), but there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as search_organizations or get_organization_profile. An agent can infer the intent but gets no guidance on edge cases like ambiguous names or missing profiles.

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