get_synonym_definition

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what it returns (the base object) but does not disclose whether the operation is read-only, requires special permissions, or how it handles missing synonyms. This is a notable gap for a tool with no annotation support.

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 a single, concise sentence that conveys the essential purpose without any unnecessary words. It is perfectly sized 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?

For a simple lookup tool, the description provides the core purpose but does not elaborate on the return value format or behavior edge cases. Given the absence of an output schema, a bit more context (e.g., what the base object looks like) would improve completeness, but the tool's low complexity makes the current description minimally viable.

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 100%, with clear descriptions for 'name', 'schema', and 'database'. The tool description adds no additional parameter information, so it correctly falls to the baseline of 3.

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 'Get the base object a synonym points to' clearly states the verb (Get) and resource (synonym) and specifies the outcome (base object). It is specific enough to distinguish from sibling tools like list_synonyms, though it does not explicitly name alternatives.

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 implies usage: use when you need to resolve a synonym to its underlying object. However, it does not provide explicit guidance on when to use it over alternatives or mention any exclusions, which places it at the 'implied usage' level.

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