get_categories

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

With no annotations, the description must carry full behavioral disclosure. It does not indicate whether this is a read-only operation (though implied by 'Lista'), nor does it describe whether results are cached, ordered, or how many categories might be returned. It also doesn't state whether the list is exhaustive or affected by other filters.

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, efficient sentence that front-loads the action and resource with no unnecessary words. It is appropriately sized for a parameterless list operation.

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 the simplicity of the tool (no parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks any behavioral context that might help an agent understand the nature of the returned list (e.g., is it a distinct set across all prompts, does it include empty results, etc.), leaving some ambiguity for a read operation.

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 tool accepts zero parameters, and the description appropriately does not discuss parameters. The baseline for zero parameters is 4, as there are no semantics to convey beyond what is already clear from the empty 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?

The description states a specific verb ('Lista') and resource ('categorias únicas dos prompts salvos'), clearly defining the scope as unique categories derived from saved prompts. It doesn't explicitly distinguish itself from the sibling get_tags, which is a similar extraction tool, but the specificity of 'categories' versus 'tags' provides implicit differentiation.

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 implies the use case (obtaining category list) but offers no explicit guidance on when to use this tool versus alternatives such as get_tags or list_prompts. There is no mention of prerequisites or contexts where it should be invoked.

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