Browse attribute folders

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds recursion behavior up to `depth`, localized path arrays, optional attribute listing via includeAttributes, and a full output shape, though it does not add permission or rate-limit context.

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 front-loaded with the browse action in a single dense paragraph. No output schema exists, so the inline output shape earns its place, though the paragraph is long and could be easier to scan.

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 a read-only browse tool with no output schema, the description supplies output shape, recursion behavior, localized path handling, and sibling routing. Annotations cover safety and the schema covers parameters, so nothing material is missing.

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 100%, so the schema already documents depth, folder path formats, attributeType enum, and includeAttributes. The description adds only 'localized' for path names and the output shape, leaving parameter semantics largely to the schema.

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?

States a specific verb, 'Browses', and resource, 'the folder structure of an attribute type', along with returned fields. It distinguishes itself from the sibling get_attributes by directing attribute details there.

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 routes the agent: use the folder paths/GUIDs with create/delete/rename_attribute_folder(s) and move_attributes_to_folder, while attribute details come from get_attributes. It names alternatives and the condition that selects them.

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