macro_uk_rightmove_monthly

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds only the source URL and return type, which are not behavioral traits such as rate limits, data update frequency, or potential errors. It provides minimal additional context beyond what annotations already offer.

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 brief but somewhat repetitive, echoing the title and using a docstring format. It includes the URL and return type, but the structure is flat and the information is thin. It is not overly long, but it under-specifies key details like data columns or units.

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 parameterless data retrieval tool, the description should explain what the returned DataFrame contains (e.g., columns, units, date range). It only states the indicator name and return type, leaving the agent without enough information to understand the output or limitations. The absence of an output schema makes this gap more significant.

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 tool has zero parameters, so the schema is complete and the description does not need to explain parameter usage. The return type is mentioned but is not parameter-related. A baseline score of 4 is appropriate for a parameterless tool.

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 identifies the tool as providing the UK Rightmove house price index monthly rate from Eastmoney, including the source URL. It distinguishes from siblings like macro_uk_rightmove_yearly by specifying 'monthly' in the name and description. However, it lacks an explicit verb (e.g., 'fetch', 'get'), so the purpose is clear but not phrased as an action.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention that this is the monthly rate and that other tools exist for yearly rates or other UK economic indicators. No exclusions or alternative tool references are provided.

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