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

No annotations are present, so description carries the burden. It mentions searching only 'active' calls and supports filtering, but does not disclose result format, pagination, or any caveats. Sufficient for a basic search tool but lacks depth.

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?

Three concise sentences: core action, usage context, and filtering capabilities. No fluff, but last sentence partially redundant with schema. Well-structured and front-loaded.

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?

All parameters are optional and documented; no output schema needed for a search tool. The description covers what the tool does and when to use it. Lacks details on response shape but acceptable for this scope.

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 each parameter is already documented. The description adds that filtering is supported, but lists 'deadline, event type, and participation mode' which do not map to specific parameters (deadline only via sort, event type/participation mode absent). Baseline 3 with minor inconsistency.

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?

Description clearly states the tool searches active academic calls for papers and research events on CallForPaper.org. It names specific use cases (conferences, workshops, CFPs, deadlines) and is distinct from siblings like analyze_abstract or get_calendar_feed.

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?

Provides explicit context for when to use: 'Use this when the user wants to find conferences, workshops, CFPs, submission opportunities, deadlines, or academic events.' Does not explicitly mention alternatives or exclusions, but sibling names are self-explanatory.

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