stock_dashboard

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

No annotations provided, and the description is too minimal to disclose any behavioral traits such as read-only, destructive potential, or output nature. Falls short of informing safe invocation.

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?

Extremely concise (3 words), but does not convey sufficient information to justify its brevity. Lacks structural elements like context or usage notes.

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?

For a parameterless tool with no output schema, the description should at least specify what KPIs are displayed. The vague 'stock (KPIs)' leaves the agent guessing about the returned data.

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?

Schema has zero parameters with 100% coverage, baseline 3. Description adds no semantic value to the empty parameter set, but no gap exists.

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?

Description 'Dashboard stock (KPIs)' vaguely identifies the tool as displaying stock KPIs, but lacks a specific verb and does not distinguish from sibling 'dashboard_kpis', which may be general KPIs.

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 'dashboard_kpis' or 'list_stock_alerts'. The agent is left to infer context from the name alone.

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