project_report

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

With no annotations available, the description carries the full burden of behavioral disclosure. It clearly indicates a read-only operation ('Get') and details what the report contains, which provides meaningful context about expected behavior. While it does not disclose potential errors or performance characteristics, it sufficiently conveys the tool's primary behavior for a report-generation tool.

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 a single, well-structured sentence that front-loads the action ('Get a summary report') and then provides concrete details. There is no redundant or extraneous information, making it highly concise and easily scannable.

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 that the tool has a single parameter, no output schema, and no annotations, the description adequately explains what the tool does and what the return value includes (pass/fail counts, coverage by feature, pending items). This is sufficient for a user to understand the tool's purpose and expected results without additional context.

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 describes the only parameter 'project' as a string with description 'Project name'. The tool description adds minimal extra meaning by referencing 'in a project', which aligns with the schema. Since schema description coverage is 100%, the description does not need to compensate much, but it also does not enrich the parameter semantics beyond the schema.

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's function: 'Get a summary report of all test cases in a project'. It specifies the resource (summary report) and scope (all test cases), and enumerates what the report includes (pass/fail counts, coverage by feature, pending items). This distinguishes it from sibling tools like list_test_cases, which would list individual cases rather than provide an aggregate summary.

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 implies usage through the phrase 'summary report' — guiding users to this tool when they need an overview rather than a detailed list. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or when-not-to-use guidance. Thus, usage is implied but not clearly delineated.

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