get_artifacts_catalog

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

No annotations are provided, so the description carries full behavioral burden. It adds content scope (data objects and annotations) beyond the bare tool name, and 'catalog' implies a read-only retrieval operation. However, it does not explicitly state that the tool returns a list, that it has no side effects, or what the response looks like, leaving some inference to the agent.

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 extremely compact, front-loaded with the key resource name, and contains only one meaningful parenthetical. There is no filler or redundancy, which is appropriate for a zero-parameter getter tool.

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 no-parameter, no-output-schema catalog getter, the description is mostly complete: it names the catalog and clarifies its contents, which is the main thing an agent needs to invoke it correctly. It is slightly thin on explicit retrieval behavior and differentiation from sibling catalogs, but those are minor gaps given the tool's simplicity.

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 has zero parameters and an empty input schema, so there is no parameter semantics burden. Per the guidelines, zero parameters receives a baseline of 4. The description and schema are consistent.

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 identifies the resource ('Catálogo de artefactos') and disambiguates it with the parenthetical '(data objects, annotations)', separating it from sibling catalog tools such as activities, markers, attributes, flow elements, and swimlanes. However, it is a noun phrase rather than an explicit verbed statement like 'returns the artifact catalog', so it stops short of fully stating the action.

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?

There is no usage guidance. The description does not mention when to choose this catalog over get_activities_catalog, get_flow_elements_catalog, get_swimlanes_catalog, or other sibling catalogs, nor does it state any exclusions or complementary relationships.

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