dictionary_at_location

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

No annotations provided; description only mentions 'offline ConceptNet' without behavioral details like read-only nature, authentication needs, or limits. Does not disclose return format or error behavior.

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?

Single sentence is concise and front-loaded with key information. However, it could include parameter hints without becoming verbose, earning a slight deduction from maximum.

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?

No output schema, no annotations, and minimal description leave significant gaps. An AI agent would lack understanding of output structure, error conditions, or how to specify language/limit parameters effectively.

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 has 0% description coverage; description does not explain parameters beyond the example. word is required but not clarified, language default 'en' not mentioned, limit range (1-1000) not indicated.

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 explicitly states the tool retrieves typical locations (AtLocation) using ConceptNet, with a clear example 'book -> library'. It distinguishes itself from sibling tools by specifying the relation type.

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?

Implied usage from name and description (find locations for a word), but no explicit guidance on when to use this tool versus alternatives like dictionary_used_for or dictionary_related. No when-not-to-use conditions.

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