retrieve_mobility_policy

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It implies read-only retrieval but does not state this explicitly, nor does it mention auth requirements, rate limits, or any side effects. The description is too sparse to inform the agent of behavioral traits.

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 sentence, making it concise. However, it is too terse and omits critical information about parameters and usage, making it under-specified rather than efficiently brief.

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 that the tool has 2 parameters with no descriptions and sibling tools that differ in purpose, the description is incomplete. It does not explain the output format (though an output schema exists) nor how to effectively use the parameters. The minimal information forces the agent to guess.

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 description coverage is 0% for both parameters ('query' and 'top_k') and the description adds no explanation of their meaning or usage. For a tool with two parameters, the absence of any parameter semantics severely hampers correct invocation.

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?

Description clearly states the tool retrieves policy passages for grounded mobility-operations guidance. The verb 'Retrieve' and resource 'policy passages' are specific, and the scope distinguishes it from sibling tools (query_charging_risk, query_mobility_metrics) which focus on risk and metrics.

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 explicit guidance on when to use this tool versus alternatives. The description mentions the domain (mobility-operations guidance) but does not provide exclusions, prerequisites, or comparative context with siblings.

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