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

With no annotations provided, the description carries the full burden of behavioral disclosure. It doesn't mention edge cases (e.g., negative values, scientific notation, rounding behavior, or whether the result is returned as a string or float), but for a simple conversion, the core behavior is adequately communicated. The description conveys that this is a read-only conversion with no side effects, which is the most important behavioral trait here.

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, short sentence: 'Feet To Meters: Convert feet to meters.' It's concise and front-loaded with the conversion. However, the title-like prefix 'Feet To Meters:' is redundant given the tool name, and the description could have used the extra space to mention precision or rounding.

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?

For a unit conversion tool with zero parameters and no output schema, the description is minimally sufficient. An agent knows this converts feet to meters, but the complete absence of parameters makes the invocation path unclear—there's no way to specify the value. In a conversational or MCP context, the agent might be expected to pass the value via the conversation, but the description doesn't clarify this. Given the extreme simplicity, this is a minor gap.

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 has 0 parameters, which is unusual—it suggests the tool either takes no explicit arguments or derives input from another mechanism. The description doesn't clarify how the feet value is provided (e.g., via a prompt conversation or implicit context), but since there are no parameters to document, the description isn't required to add param details. The task context likely provides the feet value.

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 'Convert feet to meters' is a clear statement of the conversion being performed, with the title and tool name reinforcing the exact operation. It explicitly states the input unit (feet) and output unit (meters), leaving no ambiguity about what the tool does.

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 context is self-evident for a unit conversion tool: it's used when converting from feet to meters. Since this is a simple two-unit conversion with no parameters, there's no complex alternative routing needed; however, it doesn't explicitly mention when not to use this tool (e.g., use meters-to-feet for reverse conversion), but the tool name and description make the direction clear.

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