treeflow_get_tree

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

No annotations are provided, so the description carries the burden. The verb 'Obtiene' makes clear this is a read-only retrieval operation, and it specifies what is returned (details, configuration, purpose). It does not mention error cases, permissions, or response shape, but for a simple get-by-ID these are relatively minor omissions.

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, concise sentence with no filler. It front-loads the action, resource, returned content, and identifier in a clear and compact way.

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?

For a low-complexity one-parameter tool with no output schema, the description provides a useful high-level summary of the return content and the required ID. It would be stronger if it explicitly differentiated from 'treeflow_get_tree_data' and stated read-only behavior, but it is sufficient for a basic call.

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 only parameter, tree_id, is fully documented in the schema as 'ID único del bot/árbol (UUID)' with 100percent coverage. The description merely restates 'por su ID' and adds no extra meaning about format, constraints, or behavior, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Obtiene') and resource ('bot/árbol'), and clearly states what is returned: complete details, configuration, and purpose by ID. However, it does not explicitly distinguish itself from the sibling 'treeflow_get_tree_data', so an agent could be unsure which get-tree tool to choose.

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 intended use is implied: call this tool when you need a tree's complete details, configuration, or purpose by its ID. There is no explicit when-not-to-use guidance or mention of alternatives, and the existence of 'treeflow_get_tree_data' makes some routing guidance desirable.

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