query_dmc_extractor

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

No annotations are provided, so the description carries full burden. It mentions pagination defaults but omits important behavioral details such as whether the operation is read-only, potential side effects, authentication requirements, or rate limits. This is insufficient for safe agent decision-making.

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 short and front-loaded with purpose and pagination. However, the required workflow instruction adds length and could be separated. It is mostly concise and earns its place.

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?

With 7 parameters and no output schema, the description covers purpose, pagination, and a post-use workflow. It does not describe the return format or provide examples of how to use parameters like filter, which would aid completeness. The workflow partially compensates for missing output explanation.

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 100%, and the parameter descriptions in the schema are adequate. The tool description adds no additional meaning beyond what the schema already provides, only repeating the default for top. Baseline 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 the tool queries any extractor entity in SAP DMC using OData v4, with pagination. The verb 'query' and resource 'extractor entity' are specific. It distinguishes from sibling tools by being the generic version, while siblings target specific entities.

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 includes a required workflow: compile findings and call send_report_to_teams. This provides some context on when to use it and what to do after. However, it does not explicitly state when not to use it (e.g., prefer specific query tools for extractors like query_dmc_orders) or compare with alternatives.

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