semantic_term_search

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

No annotations provided, so the description carries the full burden of disclosing behavior. It says nothing about side effects, return format, performance, or constraints. The tool may be a read-only search or may trigger something; nothing is disclosed.

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 short, but this is under-specification, not concise richness. It offers no front-loaded value and does not earn its place as a useful summary.

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 tool with 11 parameters, 0% schema coverage, no annotations, and no output schema, the description is nonexistent. An agent cannot safely or correctly invoke this tool based on the provided information.

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 0% and the description mentions none of the 11 parameters (including required ones like repository_id, target_commit, terms). Required parameters are completely unexplained, leaving the agent guessing about identifiers, formats, and semantics.

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 is a tautology: 'semantic term search' merely restates the tool name without saying what it does, what resource it operates on, or how it differs from siblings like 'search_nodes' or 'query'. Specific verb and resource are absent.

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?

No information on when to use this tool, what problem it solves, or when to prefer an alternative. Given 55 sibling tools, the agent has no basis to select this one.

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