get_reports_summary

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

No annotations are provided, so the description must convey behavioral traits. It only indicates a 'Get' operation, which implies read-only, but does not disclose any other behavior (e.g., date range support, pagination, 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 (one sentence), which is concise but underspecified. It lacks important details about parameters and usage, making it less effective despite its brevity.

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 has 3 required parameters with no descriptions and no annotations, the description is incomplete. It fails to explain the purpose of start_date and end_date or how the report is scoped. The output schema exists but is not referenced.

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%, meaning no parameter descriptions are provided in the schema, and the description adds no information about the parameters (e.g., workspace_id, start_date, end_date). The description only mentions 'for a workspace', which hints at workspace_id but not the required date range.

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 'Get time entry summary report for a workspace', specifying the verb 'Get' and the resource 'time entry summary report'. It differentiates from the sibling 'get_reports_detailed' by indicating it is a summary report.

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 provides no guidance on when to use this tool versus alternatives like 'get_reports_detailed', nor does it mention any prerequisites or context such as required filters or permissions.

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