gangtise_my_conference_list

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

No annotations provided, so description must carry behavioral context. It does not disclose read-only nature, authentication requirements, rate limits, or pagination behavior (despite 'size' and 'fetchAll' parameters). Minimal behavioral info.

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 very short but includes an irrelevant system prefix about current date, which wastes space. The substantive part is one sentence, making it concise but too brief to cover all necessary aspects.

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 10 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return format, pagination, authentication context ('my'), or how filters interact. The tool's completeness is low.

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 coverage is 50% (some parameters have descriptions). The description adds meaning for security, institution, category, and time range filters, matching the schema's documented parameters. However, parameters like 'from', 'keyword', and 'researchAreaList' are left unexplained, and the description does not compensate fully.

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 'my conference recording list' and lists filtering options (securities, institutions, categories, time range). This distinguishes it from sibling tools like 'gangtise_record_list' by specifying 'my', but lacks explicit differentiation.

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 on when to use this tool versus siblings like 'gangtise_record_list' or 'gangtise_my_conference_download'. The description only states what it does, not when it is appropriate.

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