add_glossary_term

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

Discloses upsert behavior (keeps created_at but updates definition) and return type (confirmation message). No annotations provided, so description carries burden well. Could mention if any prerequisites or side effects.

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?

Concise, front-loaded with purpose, uses structured Args section. Every sentence adds value, no wasted words.

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 2-param tool with an output schema (implied by return description), the description covers purpose, behavior, parameters, and return. No gaps given the low complexity.

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% coverage, but description provides full semantics: 'term' is unique key, reusing overwrites; 'definition' is text stored. Adds meaning beyond schema title.

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 verb 'Add' and the resource 'glossary term', with explicit upsert behavior. It distinguishes from sibling 'get_glossary' which retrieves entries.

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 context: for field-specific terms to ensure consistency. Implies when to use but lacks explicit when-not-to-use or comparison with alternatives beyond mentioning retrieval tool. Still clear intent.

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