app_encryption_declaration_documents_get_instance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: not that this is a read-only operation, not permission requirements, not whether related resources can be included, not error behavior for unknown ids. The only behavioral signal is the bare HTTP verb.

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?

It is short, but the same path is printed twice with nothing else, so no sentence earns its place. Brevity here stems from under-specification rather than disciplined concision.

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 resource-fetch tool with no output schema, the description must at least characterize the returned resource or note the field-selection behavior; it does none of that. An agent can infer almost nothing about the call beyond the URL template already present in the name.

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 both parameters (id and fields_appEncryptionDeclarationDocuments) are documented in the schema, including the enum of includable fields. That meets the stated baseline of 3, but the description adds no syntax, format, or example beyond the schema.

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 text is the raw endpoint path 'GET /v1/appEncryptionDeclarationDocuments/{id}' duplicated verbatim in parentheses, which merely restates the tool name rather than describing the operation in prose. It does imply a single-resource retrieval, so it is not misleading, but it is essentially a tautology with no explanation of what an app encryption declaration document is or what retrieving one yields.

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?

There is no guidance whatsoever about when to call this versus siblings such as app_encryption_declarations_app_encryption_declaration_document_get_to_one_relationship or app_encryption_declaration_documents_create_instance/update_instance. No prerequisites, no id-sourcing hints, no exclusions.

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