apps__app_encryption_declarations__list

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

Annotations provide readOnlyHint, idempotentHint, and destructiveHint. The description adds the GET endpoint, confirming safety. No additional behavioral context such as auth requirements, rate limits, or side effects is described. The description does not contradict 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 plus the endpoint reference, with no wasted words. It is front-loaded with the main purpose. A slight improvement could add a brief note about pagination or filtering, but it remains sufficiently efficient.

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?

The tool has 7 parameters including pagination (limit, next_url) and filtering (filter_builds, filter_platform, include, fields). The description does not explain pagination behavior, sorting, or how filters interact. However, the schema covers parameter purposes, and annotations provide safety signals. Overall, it is minimally adequate but could be more helpful for complex queries.

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%, with descriptions for all 7 parameters. The tool description adds no parameter-specific detail beyond the endpoint path, so the schema carries the burden. Baseline score of 3 applies per the rule.

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 the verb 'List', the resource 'app encryption declarations', and the scope 'belonging to an app'. It also provides the HTTP endpoint for further clarity. This distinguishes it well from sibling tools like 'app_encryption_declarations__get' which retrieves a single declaration.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as when to list vs get, or what the typical workflow would be. There is no mention of prerequisites or Related tools.

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