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

No annotations, so description carries burden. It describes the calculation and return values but does not disclose potential limitations (e.g., assumes simple gable roof) or side effects (though unlikely). Adequate but not detailed.

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?

Two sentences: first states purpose, second provides return format and pointer to related tools. No unnecessary words, efficient and front-loaded.

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 simple 3-parameter tool and description that covers input, purpose, and output, it is mostly complete. The absence of an output schema in the definition is mitigated by the return object description. Slightly lacking explicit units or constraints beyond schema, but still sufficient.

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 coverage is 100% with descriptions for each parameter. The description adds little beyond mapping 'building footprint' to length and width, and 'slope angle' to degrees. Return object is described, but parameter semantics rely mostly on 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?

Clear verb 'Calculate' and specific resource 'roof surface area' from building footprint and slope angle. Return values are listed, distinguishing it from other calculator tools in the server.

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?

Implied usage for roof area calculation, but no explicit when-to-use or when-not-to-use. Reference to 'list_bundles' hints at related tools but does not provide alternatives or exclusions.

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