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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: null/omitted parentId returns root folders plus folders shared by others including the caller's role. That is non-obvious scope semantics an agent could not infer. It stops short of describing ordering, pagination, or depth (whether it is strictly one level) — 'directas' implies non-recursive but never confirms behavior on deep trees or large result sets.

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?

Three compact sentences, front-loaded with what it lists, then the null-parent behavior, then the cross-domain caveat and downstream usage. Every sentence carries information an agent needs; nothing is redundant with the name or schema.

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 single-optional-parameter read tool with no annotations and no output schema, the description covers what an agent needs: scope, null handling, sharing semantics, and result usage. The remaining gap is the shape of the response (fields available per folder, ordering, pagination), which matters somewhat given there is no output schema to fall back on.

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%, so baseline is 3, but the description genuinely adds meaning: it explains that null and omission are equivalent, and defines what the root case actually returns (own root folders plus sharedWithMe entries with role). That is semantics the schema's 'Carpeta padre; null/omitir = raíz' only gestures at.

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 a specific verb and resource (list direct subfolders of an issues folder) and immediately states the two distinct result modes: children of a given parentId vs. root plus sharedWithMe folders when parentId is null. It also explicitly disambiguates from the sibling note-folder family ("Son independientes de las carpetas de notas"), so an agent can tell this apart from folders_list or task_folders_list without opening a 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?

Provides strong downstream usage guidance: 'Usa los id como folderId en issues_list/issues_create', which tells the agent what the results are for and which tools consume them. It lacks an explicit 'do not use this for note/task/environment folders — use X instead' statement, so routing to same-domain folder tools is only implied by the independence sentence.

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