Return fleet-standard capabilities, version, pack digest, disclaimer, composition role, and pricing.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value by listing the fields returned, but it does not disclose whether the tool has side effects, requires authentication, or has any behavioral constraints. Since no annotations are provided, the description carries the full burden; it is adequate but not comprehensive.
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 is concise and front-loaded. It uses clear, specific terms and contains no unnecessary words.
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 zero parameters and an output schema exists, the description fully covers what the tool returns. It is complete for the tool's complexity.
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?
There are zero parameters, so the description need not add parameter semantics. Schema coverage is trivially 100%, and baseline for zero parameters is 4. The description does not need to explain parameters.
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 that the tool returns 'fleet-standard capabilities, version, pack digest, disclaimer, composition role, and pricing.' It uses a specific verb ('describe') and resource ('agent'), distinguishing it from sibling tools which concern calculations, assemblies, and material packs.
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 explicit guidance on when to use this tool versus alternatives is provided. Usage is implied by the description, but there are no exclusions or alternative suggestions. For a simple zero-parameter tool, this is acceptable but not exemplary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: calculation, server info, retrieval of assemblies and material packs, listing, and verification. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., calculate_takeoff, list_assemblies, get_material_pack).
7 tools is well-scoped for a quantity takeoff server, covering listing, retrieving, calculating, and verifying without being excessive or sparse.
The tool set covers core workflows: listing, retrieval, calculation, and verification. Minor gaps like managing previous takeoffs or creating assemblies are absent but acceptable for a read-only planning estimate server.