get_activities_catalog

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

There are no annotations, so the description carries the burden for behavioral disclosure. 'Catálogo' plus the getter name imply a read-only listing with no side effects, but the description adds no explicit statements about return shape, ordering, or other behavioral details. For a zero-parameter catalog tool this is acceptable though minimal.

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 short sentence with no filler. It succeeds in being extremely concise while still naming the resource and its scope, making it easy to parse quickly.

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 zero-parameter catalog getter with no output schema, the description provides the essential information: what the catalog contains. It could mention more about output organization or typical use, but nothing critical is missing for selecting and invoking this tool.

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 no parameters, and schema coverage is effectively complete with an empty object. Per the baseline for zero-parameter tools, the description need not compensate for parameter documentation; the parenthetical 'tareas y subprocesos' adds useful content semantics about what the returned catalog covers.

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 names the resource (activities catalog) and scopes it with 'tareas y subprocesos', which helps distinguish it from sibling catalogs like markers, attributes, and artifacts. It is a noun phrase rather than a full sentence with an explicit verb, but the tool name 'get' makes the action clear.

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 usage context is implied: an agent would call this when it needs a catalog of activities/tasks/subprocesses. However, the description does not explicitly say when to prefer this over the many sibling catalog tools, nor does it mention any exclusions or alternatives.

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