Portfolio Dashboard

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

Despite no annotations, the description reveals key behaviors: the tool returns a textual confirmation if MCP Apps are not supported, the iframe makes its own tool calls, and parameters are initial only (user can switch live). It lacks mention of authentication or rate limits, but for a render tool these are not critical.

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 relatively long but well-structured, with front-loaded purpose and clear sections. Every sentence adds value, though some repetition (e.g., 'User can switch live' said twice) could be tightened.

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 simplicity (2 optional params, no output schema, no annotations), the description is thorough: it covers purpose, usage, behavior, param details, and fallback behavior. No critical gaps remain.

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 description adds context to both parameters beyond the schema: it clarifies that they are initial values and users can switch live. The enum values are listed and defaults are implied. This adds significant value for an agent.

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 clearly states it renders a portfolio tracker dashboard with specific tabs and features. It distinguishes from other types of dashboards and specifies exact user prompts that should trigger this tool.

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 explicitly states when to use ('show my portfolio dashboard', etc.) and when not to use (other dashboards like Vercel, Sentry, etc.). It advises to ask the user for clarification if ambiguous, and explains that the iframe handles its own tool calls, reducing agent burden.

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