crm_analyze_module_permissions

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

With no annotations, the description must carry the full burden of behavioral disclosure. It says 'analyze,' implying read-only, but doesn't state whether admin permissions are required, what kind of output is produced, or if any side effects exist. This leaves critical unknowns for the 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 one short sentence with no waste or redundancy, making it efficient. It could have added more substance, but brevity is not penalized here.

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?

This is a one-param analysis tool with no output schema or annotations. The description only states the general purpose and omits what the analysis includes, what the return format is, and how 'accessibility' is determined, leaving significant gaps for an agent.

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 schema has 100% coverage for the single parameter with its description 'Name of the module,' so the tool description adds no extra meaning. Baseline 3 is appropriate since the schema already documents the parameter, but no additional insight about valid values or formatting is given.

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 uses 'Analyze' as the verb and names the resource 'module permissions and accessibility,' which clearly indicates the tool's function. It doesn't explicitly distinguish from sibling analyze tools, but the resource-specific language sets it apart enough.

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?

No guidance is provided on when to use this tool versus alternatives like crm_get_module_details or crm_analyze_activity_patterns. The description gives no context on prerequisites, use cases, or exclusions.

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