sap_health_check

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

No annotations provided; description does not mention auth requirements, side effects, or whether the health check is read-only. Assumes agent knows it's non-destructive, but this is not confirmed.

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 clear sentence, no fluff. Could benefit from slightly more detail without becoming verbose.

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?

Despite having an output schema, the description remains too vague for a tool with 2 unannotated parameters and no required fields. Does not explain what the dashboard contains or how thresholds affect results.

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 coverage is 0% and description only vaguely mentions 'configurable thresholds' without linking to parameters. No explanation of 'destination' or the three profile levels.

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 it runs a SAP Basis health check dashboard with configurable thresholds, distinguishing it from sibling tools that perform more specific tasks like pinging, reading tables, or checking configs.

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 on when to use this tool versus the 18 siblings. The profile parameter (quick, standard, deep) suggests different levels but no explanation of when each is appropriate.

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