Get dashboard data

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that it is a GET operation and requires 'board_or_agent' authorization, which is valuable behavioral context beyond annotations. However, it does not describe the response behavior or any 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?

The description is very short (two sentences), but the first sentence repeats the title ('Get dashboard data') unnecessarily, making it somewhat tautological. The second sentence adds useful info. Could be more concise by removing the first sentence.

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?

While annotations cover behavioral aspects, the description fails to describe the output (dashboard data) or parameter semantics. For a retrieval tool with an output schema, the description should summarize what data is returned. It lacks completeness for an agent to fully understand the tool's effect.

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 input schema has 1 parameter (path with companyId) with no descriptions (0% coverage). The description does not explain the parameter's purpose or format. The agent receives no help in understanding what companyId means.

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?

Clear verb ('Get') and resource ('dashboard data') is stated, but no differentiation from sibling tools like pc_get_companies_by_company_id which also retrieve company data. The description identifies the specific endpoint and authorization, aiding purpose clarity.

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. The description mentions authorization class but does not specify context or exclusions. Sibling tools exist for similar company data, but no differentiation is provided.

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