get_name

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

With no annotations, the description carries the burden of disclosing behavior. 'Get information' indicates a read-only lookup, which is helpful, but the description does not clarify return format, whether exact-name matching is required, or how missing names are handled. It is adequate but minimal.

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, front-loaded sentence with no filler. It communicates the purpose and adds an illustrative parenthetical without redundancy.

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?

This is a simple one-parameter tool with no output schema, so the description is not severely incomplete. However, it does not specify what kind of information is returned or how a name should be formatted, and it lacks sibling differentiation that would help an agent choose confidently among many get_* tools.

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 already fully describes the single parameter 'name', so the baseline is 3. The description adds value by clarifying that the name refers to Sefaria entities such as Rabbis or places, which helps the agent understand the expected semantic content of the string.

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 states the verb 'Get information' and a specific resource: 'a specific name in Sefaria (Rabbi, place, etc.)'. This is clear enough to distinguish the general lookup intent, though it does not explicitly contrast with sibling tools like get_terms or get_topics.

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 usage context is implied: it should be used when you need information about a specific Sefaria name. However, there is no explicit guidance about when to prefer this over related tools, no alternatives are mentioned, and no exclusion criteria are given.

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