apps__end_user_license_agreement__get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully characterizing this as a safe read operation. The description adds no extra behavioral context beyond the endpoint, so it does not enhance transparency beyond the annotations.

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, concise sentence with the endpoint appended, making it extremely efficient and front-loaded. Every word adds value, with no unnecessary filler.

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 a simple one-parameter read operation with full annotations and no output schema, the description provides the essential purpose and endpoint, which is sufficient for an agent to invoke it correctly. It could have gone further by noting the response shape, but the simplicity of the tool makes the given context adequate.

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 single parameter 'id' is fully described in the input schema as 'ID from the matching list call,' achieving 100% schema coverage. The tool description does not add any additional meaning or context for the parameter beyond what the schema 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?

The description clearly states 'Read the end user license agreement for an app' with a specific verb and resource, and the endpoint /v1/apps/{id}/endUserLicenseAgreement confirms the action. This distinguishes it from related tools such as apps__beta_license_agreement__get and end_user_license_agreements__get by specifying the 'end user' agreement for an app.

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 like apps__beta_license_agreement__get or end_user_license_agreements__get. The description only states the action without any usage context, exclusions, or alternative scenarios.

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