tiendanube_get_metafield

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

No annotations are present, and the description only states 'Retrieve' without disclosing behavioral traits such as read-only nature, authentication needs, rate limits, or error handling. The description provides minimal behavioral context for a read operation.

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 very concise at one sentence, with no redundant words. The 'GET METAFIELD' prefix front-loads the action. It could be slightly improved by adding brief context, but overall it is appropriately sized for a simple tool.

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 the absence of output schema and annotations, the description lacks details about the return value, including structure or example. It also does not specify potential errors (e.g., not found). The tool is simple but the description is incomplete for an agent to fully understand the behavior.

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 single parameter 'metafield_id' is only defined in the input schema with type and required flag; the description does not add any additional meaning or context about the parameter, such as format or source, beyond what is obvious from the tool name.

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 'Retrieve' and the resource 'metafield', and specifies the retrieval by ID. It effectively differentiates from list_metafields and other metafield operations.

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?

No explicit when-to-use or alternative guidance is provided, though the context of sibling tools like create_metafield and list_metafields implies when this tool is appropriate. The description lacks direct exclusions or conditions.

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