get_bizagi_extended_info

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

No annotations are provided, so the description carries the full disclosure burden, yet it reveals almost nothing about behavior. It does not describe the returned content, operational constraints, or any side effects.

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 short, but the brevity reflects under-specification rather than effective conciseness. The phrase adds little value and is not structured in a way that helps an agent understand what the tool actually provides.

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?

With no output schema and no annotations, the description needed to explain what 'extended information' means and what the agent will receive. It does neither, leaving the tool ambiguous among many sibling reference and catalog tools.

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 input schema has zero parameters, so there are no parameter semantics for the description to clarify. The zero-parameter baseline is 4, and no schema coverage gap exists.

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 'Información extendida de Bizagi Modeler' is essentially a translation of the tool name, so it restates rather than explains. It does not specify what information is included and does not distinguish the tool from siblings such as get_bizagi_specifics or get_bpmn_cheatsheet.

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 guidance on when to call this tool instead of any of the many sibling information or catalog tools. The description implies that it returns information but provides no use cases, exclusions, or alternatives.

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