list_committees

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

No annotations provided. The description discloses return format (JSON string) and error behavior (Chinese message), but lacks details on read-only nature, rate limits, or required permissions.

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 structured with Args, Returns, Raises. It is reasonably concise but could be shortened (e.g., remove redundant parameter descriptions already in schema).

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?

Given the 5 optional parameters and existing output schema, the description covers basic use. However, it lacks context on pagination behavior, filtering logic, or typical usage patterns.

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 baseline is 3. The docstring repeats the same parameter descriptions as the schema, adding no extra meaning.

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 '列出委員會列表' clearly indicates the tool lists committees. However, it is somewhat tautological ('list committee list') and does not distinguish from siblings like get_committee or list_meets.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., get_committee for a single committee). The description only lists parameters without contextual advice.

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