Phenomenai

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it returns up to 10 matching terms with summaries, implying a limit and format, but lacks details on permissions, rate limits, or error handling. This is adequate but leaves gaps for a search tool.

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 appropriately sized and front-loaded: the first sentence states the purpose, the second specifies the return limit, and the 'Args' section efficiently details parameters. Every sentence adds value without waste.

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's moderate complexity (2 parameters, no annotations, but has an output schema), the description is mostly complete. It covers purpose, usage, parameters, and return behavior, but since an output schema exists, it need not explain return values. Slight improvement could include error cases or search specifics.

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 description coverage is 0%, so the description must compensate. It adds meaning beyond the schema by explaining that 'query' matches against term names, definitions, and tags, and provides examples for 'tag' (e.g., 'cognition'). This clarifies usage effectively, though it could detail format constraints more.

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's purpose with specific verbs ('Search the AI Dictionary') and resources ('by keyword and optional tag filter'), and distinguishes it from siblings like 'lookup_term' (which likely retrieves a single term) or 'dictionary_stats' (which provides statistics rather than searching).

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?

The description provides clear context for when to use this tool (searching with keywords and optional tags) but does not explicitly state when not to use it or name alternatives among siblings, such as 'lookup_term' for direct term retrieval or 'list_tags' for tag exploration.

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