get_dashboard_summary

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

With no annotations, the description must fully disclose behavior. It mentions return fields (success, summary) but omits behavioral details such as idempotency, side effects, or error handling. Additionally, the description states caller_agent_id is required while the schema marks it optional, causing confusion.

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 and uses a clear Args/Returns structure. However, the inconsistency with the schema reduces its value, preventing a higher score.

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 presence of an output schema (implied) and only one parameter, the description lacks completeness. It does not mention error conditions, prerequisites, or how this tool relates to 'get_dashboard'. The contradiction with the schema further undermines completeness.

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 description coverage is 0%, so the description must compensate. It adds a brief explanation for caller_agent_id but incorrectly claims it is required, contradicting the schema. This misleads about parameter usage.

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 the tool retrieves a dashboard summary, using a specific verb and resource. However, it does not differentiate from the sibling tool 'get_dashboard', leaving ambiguity about what a 'summary' entails versus the full dashboard.

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 is provided on when to use this tool versus alternatives like 'get_dashboard'. There is no context about prerequisites or expected use cases.

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