crm_get_dashboard

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

No annotations are provided, so the description must fully disclose behavior. It only repeats the action ('Get') without explaining side effects, safety, return format, or any constraints. This is especially problematic for a tool that likely reads data, but nothing is explicitly stated.

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 short sentence with no redundancy, which is efficient. However, it is under-specified, but conciseness focuses on economy of language, not completeness. It earns a 4 for being tight and to the point, though it could have been more informative.

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 presence of sibling tools and the lack of annotations or output schema, the description is grossly incomplete. It does not specify what metrics are returned, how it differs from crm_get_pipeline, or what an agent should expect. This is inadequate for a tool with this level of ambiguity.

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 schema coverage is 100% (trivially, as there are no properties). Baseline for 0 params is 4. The description adds no parameter information, but none is needed since there are no parameters to explain.

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 states a clear verb ('Get') and resource ('CRM dashboard') but is vague about what the dashboard contains. It does not distinguish it from sibling tools like crm_get_pipeline, which could also provide pipeline metrics. The purpose is understandable but lacks specificity to uniquely identify this tool among alternatives.

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 use this tool versus alternatives. The description does not mention any context, exclusions, or conditions. With multiple related CRM tools (crm_get_pipeline, crm_get_timeline, etc.), the lack of usage guidance leaves the agent to guess.

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