build_get_last_report

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

With no annotations provided, the description carries full burden but omits whether the operation is read-only, any side effects, performance impact, or required context. It does not disclose if 'scan' modifies data or just queries.

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 sentence that immediately conveys the tool's output deliverables without redundancy. However, it sacrifices completeness for 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 lack of output schema and incomplete parameter documentation, the description fails to provide sufficient context about the report format, asset types included, or how 'top largest' is defined. The sibling tools suggest build analysis but no explicit link.

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 schema coverage is 0% and the description adds no explanation for the only parameter 'topN'. The default value is present but meaning, constraints (e.g., min/max), and behavior are undocumented.

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 mentions scanning a project and returning top largest assets, size by extension, and total size, but uses the vague verb 'scan'. It somewhat distinguishes from siblings like 'build_analyze_bloat' but could be more specific about the exact resource being reported.

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 like 'build_analyze_bloat'. No exclusions or prerequisites are mentioned, leaving the agent without decision support.

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