get_folder_path_hierarchy

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

No annotations are provided, so the description must disclose behavioral traits. It does not state whether the operation is read-only, if it requires special permissions, or any side effects. The absence of such information leaves an agent without critical context for safe invocation.

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 short sentence, making it concise and front-loaded. However, it is too brief given the lack of additional elaboration in the schema or annotations. A slightly longer description would improve clarity without sacrificing conciseness.

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?

Despite the existence of an output schema, the description is insufficient. It does not explain the return value (breadcrumb format) or provide enough context for the agent to use the tool effectively, especially given the two required parameters are undocumented.

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 input schema has two required parameters (folder_id, matter_id) with no descriptions. The schema description coverage is 0%, but the description does not add any explanation about these parameters, leaving the agent without understanding of what values to provide.

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 states 'Get the full path hierarchy (breadcrumb) to a folder.' It uses a specific verb 'Get' and identifies the resource 'folder path hierarchy'. This clearly distinguishes it from sibling tools like 'get_folder_contents' (which retrieves folder contents) and 'get_root_folder_contents'.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of when not to use it or any context that helps the agent decide between this and related tools like 'get_folder_contents' or 'get_folder_history'.

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