fmod_system_getNumber

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

The description notes that the tool is 'blocking' and returns null on cancellation, which are key behavioral traits. However, since no annotations exist, more detail could be beneficial, such as whether it waits indefinitely or has a timeout, and how it handles non-numeric input. Adequate but not fully transparent.

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 very short, with one meaningful sentence and a note on optional args. It is front-loaded with the core action. The inclusion of '[method · system.getNumber]' is extraneous but not harmful. Could remove the bracketed note for better 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?

The tool is simple with no output schema, so the description adequately covers the basic flow. However, it lacks detail on input validation (e.g., whether it rejects non-numeric strings) and the response format beyond 'returns the value.' Completeness is middling.

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 50% (only defaultText has a brief 'optional' note). The description adds 'bracketed args are optional' but does not explain the purpose or format of msg or defaultText. Given low coverage and minimal added meaning, this dimension scores low.

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 the tool 'prompts for numeric input and returns the value, or null if cancelled (blocking).' This specifies the action (prompting) and resource (numeric input from the system), and it differentiates from sibling tools like getFile or getText by focusing on numbers.

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 is provided on when to use this tool versus alternatives. The description does not mention contexts where numeric input is needed or when to prefer it over other input methods, 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.