List categories and tags

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the actual return shape, which matters because there is no output schema. It does not mention household size limits, empty-category behavior, or performance, so it falls short of full disclosure but is well above baseline.

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 return contents come first and the call-to-action guidance second, which is the right order. The first sentence is long and parenthetical-heavy, but each clause (categories, tags, templates) earns its place by naming distinct output data.

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?

With no output schema, the description carries the burden of explaining return values, and it does so for all three result sets including the nested extra-field concept. Missing only edge-case behavior such as empty households or output size, which is minor for a zero-parameter read.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a no-param tool is a 4; nothing here contradicts or omits parameter meaning.

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?

Names the three resources returned (categories as a tree, tags with counts, item templates) with concrete detail about what each contains — ids, paths, item counts, extra fields. That level of specificity distinguishes it from sibling lists like list_locations or list_collections without needing the schema.

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 says to call it before create_item or update_item, and states the three lookups it supplies (categoryId, existing tag names to avoid near-duplicates, templateId) plus the downstream step of placing values in customFields by key. That is a concrete when-to-use trigger tied to named siblings.

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