gangtise_forum_list

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

The description includes a practical note about the current date and timezone, which helps interpret temporal queries. However, it does not disclose that the tool is read-only, whether authentication is required, or how pagination works (though schema includes 'size' and 'fetchAll'). With no annotations, the description partially fills the gap but lacks key behavioral details.

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 concise, with the date instruction front-loaded for immediate context. The second sentence states the purpose. It is not overly long, but the date instruction could be integrated into parameter descriptions to reduce repetition.

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 tool has 15 parameters, low schema coverage, and no output schema, the description is insufficient. It does not explain default behaviors, sorting, or return format. The date instruction adds some context, but overall the description leaves many gaps that an agent would need to infer or test.

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 description lists filter categories (research area, institution, etc.) that correspond to parameters, but provides no details on valid values, formats, or how to combine them. With only 33% schema coverage for parameters, the description should compensate, but it only adds a high-level overview, leaving many parameters underspecified.

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 states the tool queries a forum schedule list and lists filter dimensions (research area, institution, security, etc.). The name 'gangtise_forum_list' reinforces the purpose. However, it does not explicitly differentiate from sibling list tools, relying solely on the name and description context.

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 guidance is provided on when to use this tool versus alternatives like gangtise_announcement_list or gangtise_drive_list. The description only states what the tool does, not when it should be preferred. This omission requires the agent to infer use cases from the name.

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