her_get_scotland_record

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the tool retrieves a single record and describes the return format and fields (site type, form, location, grid reference). It does not mention side effects or permissions, but these are likely minimal for a read-only lookup tool.

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 concise and well-structured: a clear title sentence, followed by a brief explanation, labeled Args and Returns sections, and a practical tip for LLMs. Every sentence adds value with no 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?

The tool is simple with two parameters and no output schema, but the description explains return fields adequately. It could mention error handling or rate limits, but for a read-only lookup tool, the coverage is sufficient for correct usage.

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 with no descriptions for the two parameters. The description fully compensates by explaining record_id accepts two formats ('scotland:CANMOREID' or just the ID) and output_mode options ('json' default or 'text'), adding crucial meaning beyond the bare schema.

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 'get' and the resource 'Scottish NRHE record', specifying it retrieves full details by Canmore ID. It distinguishes from sibling tools like her_search_scotland by focusing on retrieval of a single record.

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 advises using record_id from her_search_scotland results, providing clear context for when to use this tool. However, it does not explicitly mention when not to use it or suggest alternatives.

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