sap_get_page

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

With no annotations, the description must fully disclose behavioral traits DNA. It only states the action and output, but omits critical details such as authentication requirements, error handling, potential side effects (e.g., session state changes), or rate limits. It also fails to note whether it modifies data or is purely read-only, which is significant given the WebGUI context.

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 one sentence, concise, and front-loads the primary action. However, it omits essential details that could be included without bloat, so it's efficient but potentially under-specified.

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 tool's complexity (interfacing with SAP WebGUI), the description is insufficient. There is no output schema and no annotations; the description does not explain return format, potential errors, session dependencies, or navigation side effects. Sibling tools suggest a need for orchestration (e.g., login before fetch), but that is not documented.

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?

The only parameter, url_path, has a schema description that covers 100% of its content (explains it's a relative path with example). The tool description adds no additional semantics beyond what the schema provides, so 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 'Fetch any SAP WebGUI URL and return the rendered page text' clearly states the verb (fetch) and resource (SAP WebGUI URL), and specifies the output (rendered page text). It distinguishes from siblings like sap_run_report or sap_execute_command, which perform other actions, though it does not explicitly contrast with them. The scope 'any' implies flexibility but not exact differentiation from other fetch-like tools.

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 is provided on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites (e.g., requiring sap_login first), or when to choose sap_execute_command or sap_run_report instead. The context of 'any URL' implies broad use, but there is no roadmap for decision-making.

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