crm_get_global_set_values

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

With no annotations, the description carries the full burden of behavioral disclosure, but only says 'get' and 'extracting'. It does not disclose whether the operation is read-only, what the return structure looks like, or how include_metadata affects results. This leaves significant ambiguity for an 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 a single, front-loaded sentence that efficiently conveys the core action and scope. The phrase 'specifically for extracting complete disposition data' is a bit redundant with the tool's purpose but does not add meaningful bloat.

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?

Basic invocation is covered by the schema and short description, but the tool lacks an output schema and the description omits key context like what 'complete disposition data' means, whether metadata is included by default, and how this differs from sibling disposition-related tools. This leaves gaps for an agent deciding between 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 already provides full descriptions for both parameters, including the example 'Disposition' for global_set_name and the default false for include_metadata. The description's reference to 'by name' adds little beyond the schema, so it stays at the schema-driven baseline of 3.

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 verb 'Get' and resource 'Global Set values by name', and narrows scope with 'specifically for extracting complete disposition data'. This distinguishes it from generic getters, though the sibling crm_get_complete_disposition_data suggests potential overlap, preventing a 5.

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 phrase 'specifically for extracting complete disposition data' implies intended usage, but there is no explicit when-to-use guidance or mention of alternatives. The description does not explain when to prefer this tool over crm_get_complete_disposition_data or crm_get_picklist_values.

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