fluig_ged_path

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

No annotations are provided, so the description carries the full burden. 'Breadcrumb'/'resolve' implies a read-only lookup, but nothing states the return shape (list of folders? ids and names? root-to-parent order), nor what happens when documentId does not exist or the env host is unreachable.

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?

Two compact sentences: identity first, then the reason to call it. Nothing is wasted and the operative guidance is front-loaded after the purpose clause.

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 annotations and no output schema, the definition should say what a resolved path looks like and how failures surface, since 'path' could be a delimited string or a folder chain. It covers purpose and motivation but leaves the result contract and error behavior unspecified.

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 coverage is 100% and the env parameter is explained at length in the schema (teste vs prod, no default). The description only echoes the root traversal implied by rootId, adding nothing on documentId or rootId semantics beyond the schema. Baseline 3 applies.

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?

Specific verb + resource: 'resolve o caminho de um documento desde a raiz' clearly states it returns a GED breadcrumb path for a document. It is distinguishable from fluig_ged_list (enumeration), fluig_ged_download (content) and fluig_ged_upload (writes), though no sibling is named explicitly.

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?

Gives a concrete triggering scenario: use it to find out where a document actually lives before publishing something next to it. No when-not conditions or explicit alternatives are offered, but the intended workflow is clear.

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