connects_dashboard

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds only 'personalized' and 'discovery recommendations', implying user-specific output, but does not disclose pagination, personalization details, or behavior when the view parameter is omitted. No contradiction with annotations.

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 sentence with no filler, and the core resource is front-loaded. The phrase 'dashboard or discovery recommendations' is slightly ambiguous, which prevents a perfect score.

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?

With one optional enum parameter, an output schema, and safety-related annotations, the description is mostly adequate for a simple tool. Still, it does not explain how the view parameter changes the response or when this dashboard tool should be preferred over sibling connects_* 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 schema exposes a single optional 'view' parameter with a self-descriptive enum and default value. However, schema description coverage is 0%, and the description does not explain what each enum value returns or how 'discovery recommendations' maps to the available views.

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 names the resource ('IE Connects dashboard or discovery recommendations') and mentions personalization, but it lacks an explicit verb such as 'returns' or 'fetches'. It also does not clearly distinguish this dashboard entry point from sibling tools like connects_feed or connects_activity.

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 given about when to use this tool versus alternatives, such as connects_feed, connects_activity, or blackboard_dashboard. There are no conditions, alternative suggestions, or exclusion criteria beyond what can be inferred from the tool name.

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