stape_get_store_document

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only says 'Retrieve' and the source, but does not explain what happens if the key is missing, whether it is read-only, or any return format details. This is a significant gap for a tool with no structured annotations.

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 redundant words. It efficiently conveys the action, resource, and context in an immediately scannable way.

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 simple getter with complete schema coverage and no output schema, the description is minimally adequate. However, it lacks any mention of error handling (e.g., missing key) or the structure of the returned JSON, which could be important for the agent to set expectations. Given the low complexity, this is acceptable but not comprehensive.

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 provides 100% coverage of both parameters, so the description adds minimal extra meaning beyond restating 'by key' and 'from Stape Store'. It does not enrich the parameters with format, constraints, or examples, so the baseline of 3 applies.

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 tool retrieves a JSON document by key from Stape Store, using the specific verb 'Retrieve' and naming the resource. It distinguishes from sibling tools by being the read operation among store document actions (set, delete).

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 implies when to use this tool (when you need to read a document) but provides no explicit alternatives or exclusions. It does not mention that set/delete are for writing, nor does it state any context where this tool should not be used.

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