get_distribution_profile_details

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

With no annotations, the description carries the full burden. It accurately discloses that the return excludes settings.password, includes pagination for app versions, and provides error envelope structure. However, it does not explicitly state read-only nature (though implied) or authorization needs.

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 well-organized into sections: purpose, returns, args, examples. Every sentence provides necessary information without verbosity. It is appropriately sized for the tool's complexity.

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 description covers purpose, parameters, return format including pagination, and provides usage examples. Given the presence of an output schema, it does not need to explain return fields in detail. It is complete for a detail retrieval tool.

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 description fully explains each parameter: profile_id as a UUID, page as 1-based integer defaulting to 1, size as 1-100 capped at 100 with default 25. This adds significant value beyond the schema, which had 0% description coverage.

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 it gets a single testing distribution profile by ID with optional app versions pagination. The verb 'Get' and resource 'distribution profile' are specific, and it distinguishes from sibling list tool 'get_distribution_profiles' by focusing on a single profile with details.

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?

The description implies usage via the 'Get a single ...' phrasing, but it does not explicitly state when to use this tool over alternatives like 'get_distribution_profiles'. No when-not or alternative guidance is provided.

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