update_crm_endpoints

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

No annotations provided, so description must fully disclose behavior. It labels the tool as [mutation] and mentions confirmation requirement, but does not explain what happens when executed (e.g., whether it overwrites existing endpoints, side effects, or required permissions). The parameters clarify add/remove behavior, but the description itself is vague.

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, concise sentence that conveys the core purpose and a key requirement (confirmation). It is front-loaded with the tool's action. However, it could be structured more clearly with separate notes.

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 tool has 3 parameters, no output schema, and no annotations, the description provides minimal context. It covers the purpose and confirmation requirement but lacks details on return value, effect on existing endpoints, and prerequisites. The schema descriptions fill some gaps, but overall completeness is moderate.

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% with parameter descriptions already present. The description adds the confirmation requirement context, which is linked to the confirm parameter. However, no additional semantic meaning beyond the schema is provided.

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 clearly states the tool configures CRM endpoints for data synchronization, using specific verb 'Configurar' (configure) and resource 'endpoints CRM'. It distinguishes itself from siblings by focusing specifically on CRM endpoint configuration, even though sibling list includes many update tools, this is unique.

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 mentions that confirmation is required (confirm=true) but does not provide explicit guidance on when to use this tool versus alternatives like test_crm_endpoint or reset_crm_errors. It implies usage for syncing data but lacks exclusions or alternatives.

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