crm_get_all_profiles

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

With no annotations, the description must carry behavioral detail. It adds 'Prerequisites: None' and error recovery advice, implying a read-only discovery operation. However, it does not explicitly state that the operation is read-only, what the return format looks like, or any pagination/limits. Thus it provides some context but not full transparency.

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 front-loaded with the main purpose and then uses structured sections for prerequisites, next steps, common pattern, and error recovery. This is easy to scan and mostly efficient. Minor redundancy exists between 'Next Steps' and 'Common Pattern,' but it remains concise.

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's low complexity (no params, no annotations, no output schema), the description is quite complete. It explains the purpose, provides workflow context, and offers error recovery. It could mention return value specifics, but for a simple discovery tool, the provided context is sufficient.

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 the schema already reflects this (empty properties). Per the rubric, 0 params sets a baseline of 4. The description does not need to add parameter details; it correctly focuses on the tool's purpose.

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 is a clear, specific statement: 'Get all profiles in the organization.' It identifies the verb (get), resource (all profiles), and scope (organization). This distinguishes it from siblings like crm_get_all_roles (roles vs. profiles) and config_list_profiles (organization vs. configuration context).

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 provides clear usage context through 'Prerequisites: None - this is a discovery tool for organizational structure' and outlines a common workflow with 'Next Steps.' It does not explicitly state when not to use it or name alternative tools, but the discovery role and workflow guidance make the intended use clear.

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