get_dashboard_assistant

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

No annotations are provided, so the description carries full burden. It states this is a 'get' operation (likely read-only) and mentions 'authenticated user', but doesn't disclose behavioral traits like permissions needed, rate limits, response format, or whether it returns a specific type of assistant. For a tool with zero annotation coverage, this is insufficient.

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?

Single sentence, front-loaded with the core action, no wasted words. Every word earns its place by specifying the action, target, and user context efficiently.

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 no annotations, no output schema, and a simple zero-parameter tool, the description is incomplete. It doesn't explain what a 'dashboard assistant' is, what data it returns, or how it differs from other get_* tools. For adequate context, it should clarify the resource scope and output expectations.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, but that's appropriate here. Baseline is 4 for zero-parameter tools when schema coverage is complete.

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 'Get the dashboard assistant for the authenticated user' clearly states the action (get) and target (dashboard assistant), but it's vague about what a 'dashboard assistant' is and doesn't distinguish from siblings like get_assistant or get_one_assistant. It provides basic purpose but lacks specificity about scope or resource type.

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 on when to use this tool versus alternatives like get_assistant or get_one_assistant. The description implies it's for the authenticated user, but doesn't specify prerequisites, exclusions, or comparison to sibling tools. Usage context is minimal.

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