sap_read_change_docs_v2

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

No annotations are provided, so the description carries the full burden. It only says 'query using function modules' and 'optimized,' which implies a read operation and some performance benefit, but does not disclose return shape, side effects, authorization needs, or limits beyond what the schema shows. This is minimal for a tool with no annotation support.

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?

One short sentence with front-loaded verb and resource, then a differentiator and a preference. No filler; every phrase 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?

For an 8-parameter tool with no output schema, the description is functionally complete for selection but thin on what the returned data looks like. The schema fills parameter details, and the purpose/preference are clear, so it is adequate but leaves return-structure guessing.

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%, so the baseline is 3. The description adds emphasis on tabname filtering, but does not enrich parameter semantics beyond what the schema already provides.

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?

States a specific verb ('query') and resource ('change document') and explicitly positions itself as the optimized/preferred variant over the legacy endpoint, which distinguishes it from sibling sap_read_change_docs. The mention of 'using function modules' and 'additional filtering by table name' further clarifies scope.

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?

Explicitly says 'Preferred over legacy endpoint,' telling the agent to choose this over the older change-doc endpoint. It also highlights the additional table-name filter as a selection factor. It does not name the legacy sibling or give exclusion conditions, so not a 5.

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