get_project_dashboard

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

Describes a read-only view ('View') and lists displayed data. No annotations exist, so description carries full burden; it is mostly transparent but could explicitly state it is read-only and has no side effects.

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?

Two sentences with no fluff; first sentence front-loads purpose and data shown, second provides alternative tool. Highly concise and well-structured.

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?

Tool has no parameters and has an output schema, so description doesn't need return value details. It fully covers purpose, data provided, and differentiation from sibling, making it complete for this simple tool.

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?

Input schema is empty with 100% coverage; baseline for 0 parameters is 4. Description does not need to add parameter info and correctly omits it.

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 clearly states the tool views the PM project dashboard for active projects, listing specific metrics. It distinguishes from sibling get_my_projects by noting it is the Project Manager view, not the personal allocation list.

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?

Explicitly says when to use (view dashboard for active projects) and when not (for personal allocation, use get_my_projects instead), providing clear alternatives.

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