her_get_conservation_area

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

No annotations provided. Description covers input formats, output modes, and return content (name, LPA, location) but omits details like read-only nature, error handling, or rate limits.

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?

Well-structured with sections, but could be slightly tighter. Every sentence adds value, including the LLM tips. Appropriate length for the tool's simplicity.

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?

Adequately describes return values ('Full details including name, LPA, location') despite no output schema. Context from siblings confirms it's a specific getter. Small gaps in behavior details.

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?

Adds significant value beyond schema (0% coverage). Explains record_id accepts 'ca:UID' or plain UID, and output_mode defaults, with examples.

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?

Clearly states 'Get full details of a specific conservation area' using a specific verb and resource. Distinguishes itself from sibling search tools by focusing on retrieval by UID.

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 clear context on when to use (retrieve by UID) and includes LLM tip to use record_id from search results. Does not explicitly state when not to use or compare to other get tools.

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