get_distribution_profiles

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

With no annotations, description carries full burden. It discloses pagination, search filtering, default values, capping behavior, exclusion of sensitive data (password), and return envelope structure. Does not mention authorization or rate limits, but is transparent for a read-only tool.

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?

Description is well-structured: summary, return content, parameter details, return envelope, and examples. Every sentence adds value, though could be slightly more concise. Front-loaded purpose helps quick understanding.

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 (3 optional parameters, no enums, output schema exists), description covers all aspects: parameter explanations, behavior constraints, return format, and examples. Includes privacy note about password exclusion. Complete for a paginated list 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?

Schema has no descriptions (0% coverage), but description explains each parameter: page (1-based, default 1), size (range 1-100, capped), search (case-insensitive partial match with example). These details add critical meaning 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?

Description clearly states the verb 'Get' and resource 'testing distribution profiles for the current organization (paginated)'. It specifies the returned fields (IDs, names, versions, etc.) and the optional filter, distinguishing it from sibling tools like 'get_build_profiles' or 'get_store_profiles'.

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?

Description explains the purpose and optional search parameter, but does not explicitly state when to use this tool versus alternatives or provide 'when not to use' guidance. Examples show typical usage, but no sibling comparison.

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