simpleshop_get_metadata

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

No annotations are provided, so the description carries full responsibility. It only states 'Return... metadata', implying a read operation, but gives no details on side effects, authentication needs, rate limits, or output behavior. This is insufficient for a tool with 6 parameters.

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 one short sentence, which is concise but lacks structure. It is not front-loaded with the most critical information (e.g., parameters). Every sentence earns its place, but more content is needed to be helpful.

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 annotations, 6 parameters without descriptions, and no output schema details in the description, the tool is severely under-documented. The description does not explain what metadata categories are, how to use the boolean flags, or what the return value contains.

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 description coverage is 0% and the description does not mention any parameters. Each of the 6 boolean parameters controls inclusion of metadata categories, but the description adds no meaning beyond the schema defaults.

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 action ('Return') and resource ('SimpleShop metadata'), and hints at its purpose ('useful for filtering and accounting classification'). It is distinct from sibling tools which focus on documents and products, but could be more explicit about what metadata covers.

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 offers no guidance on when to use this tool versus alternatives, no when-not-to-use conditions, and no mention of prerequisites or context. The single sentence only provides a general purpose.

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