Info value

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

Annotations already declare readOnlyHint true and openWorldHint true, so the description does not need to cover safety or return variability. It adds the behavioral detail that the value is addressed by section and id, which is useful but not extensive. No contradiction with annotations.

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, focused sentence that immediately conveys the action and includes a clarifying example. It is front-loaded and free of filler, earning a top score for conciseness.

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 simple read-only getter with fully documented parameters, the description sufficiently covers the main purpose. It does not describe the return format, but openWorldHint indicates arbitrary return types, reducing the need for that detail. The tool is simple enough that this description is nearly complete.

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 descriptions already cover 100% of the parameters with meaningful explanations and examples. The tool description only repeats the example, adding no new semantic value beyond what the schema provides. Baseline of 3 is appropriate.

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 'Return a single file-info value' with a specific addressing mechanism via section and id names. It provides concrete examples for both parameters, making the tool's function unmistakable and distinct from sibling tools like banana_infos or banana_info_table.

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 for retrieving one specific info value by section and id, but does not explicitly contrast it with alternatives such as banana_infos (which likely returns multiple). The phrase 'single' hints at the use case, but there is no explicit when-to-use or when-not-to-use guidance.

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