SAP Smart Query Router

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'routes' but doesn't explain what this entails (e.g., returns a tool recommendation, invokes another tool, requires authentication, has rate limits, or handles errors). For a routing tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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, efficient sentence with no wasted words, making it appropriately concise. However, it's under-specified rather than truly front-loaded with useful information, slightly reducing its effectiveness.

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 the complexity (routing logic, 2 parameters with nested objects, no output schema, and no annotations), the description is incomplete. It doesn't explain what the tool returns (e.g., a tool name, structured data), how routing decisions are made, or any behavioral constraints, leaving too many gaps for effective use.

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%, so the description must compensate for undocumented parameters. It adds no meaning beyond the schema, failing to explain 'userRequest' (e.g., natural language query) or 'context' fields (e.g., 'serviceId', 'entityType'). With 2 parameters and nested objects, this gap is significant.

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 'Routes SAP requests to optimal tool' restates the title 'SAP Smart Query Router' with minimal elaboration, making it tautological. It doesn't specify what 'routes' entails (e.g., analyzing requests, selecting tools) or what 'optimal' means, leaving the purpose vague compared to siblings like 'natural-query-builder' or 'search-sap-services'.

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. With many sibling tools (e.g., 'natural-query-builder', 'smart-data-analysis'), the description lacks context on its role (e.g., as an entry point or dispatcher), prerequisites, or exclusions, offering no help in tool selection.

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