describe_hands_schema

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

No annotations provided, so description covers all: static document, no file/DB reads, read-only, no side effects, auth, or rate limits. No contradictions.

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?

Three sentences: purpose, behavioral details, and usage guidance. No filler; each sentence adds distinct value.

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?

Given no output schema, description adequately conveys what is returned (schema, validation rules, etc.) and its purpose. Contextually complete for the tool's simplicity.

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?

Tool has zero parameters; schema coverage is 100% (empty). Description confirms 'takes no parameters'. Baseline 4 applies as per rules.

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 it returns the complete authoring reference for 'kontexta.json', including schema, validation rules, security guarantees, limitations, and an annotated example. It distinguishes itself from sibling tools like list_hands and reload_hands by specifying its static, read-only nature.

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?

Explicitly states when to use (helping write/fix kontexta.json) and when not to, naming alternatives: 'to see the loaded tools themselves use list_hands; to apply edits use reload_hands.'

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