amac_person_fund_org_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only the source URL and return type but does not disclose behavioral details like pagination, data freshness, authentication needs, or how the 'symbol' parameter affects the result scope.

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 description is moderately sized but structured as a docstring with a title, URL, and parameter/return sections. The purpose is not front-loaded as a concise sentence, and the URL and lengthy choice list add bulk without a clear functional summary. It is not overly verbose, but could be improved by adding a one-line operational description at the top.

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 one parameter and no output schema, the description covers the essentials: parameter choices, type, return type, and source URL. However, it doesn't specify the columns or contents of the returned DataFrame, and it lacks a clear behavioral overview, leaving the agent with an incomplete picture for a simple tool.

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 schema's 'symbol' property has no description (0% schema description coverage), so the description is the sole source of parameter semantics. It provides a comprehensive list of valid choices, the type (str), and the meaning (organization type), which is essential for correct invocation. However, it doesn't explain the default behavior when 'symbol' is omitted beyond what the schema default indicates.

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 opens with a Chinese title '基金从业人员资格注册信息' (fund practitioner qualification registration information) and then provides parameter/return docs, but it lacks an explicit verb phrase stating what operation is performed. The tool name contains 'list', implying retrieval of a list, but the description doesn't clearly say 'list fund practitioners by organization type' nor does it distinguish itself from the similar sibling amac_person_bond_org_list.

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 guidance on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, exclusions, or name any sibling tools such as amac_person_bond_org_list, making it hard for an agent to decide between similar AMAC tools.

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