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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond annotations: the required 'properties' scope (auth need) and the optional flag set that changes the shape of the response.

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?

Front-loaded with the returned fields, then flags, then scope, then the raw endpoint. Three efficient sentences with little waste, though the trailing 'Beds24: GET /properties' adds marginal value to an agent.

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 an 11-param, no-required, no-output-schema read tool, the description covers the return shape, optional flag behavior and auth scope adequately. Pagination and language/price-rule nuances remain only in the schema, a minor gap.

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 coverage is 73% (above 50% but below 80%), so the schema documents most parameters. The description summarizes several flags (texts, pictures, offers, unit details, all rooms), adding orientation, but omits page, roomIds, propertyIds, includeLanguages, includePriceRules and includeUpsellItems, so it does not fully compensate.

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?

Clear specific verb+resource: 'List the properties in the account' and it enumerates what is returned (address, currency, check-in times, room types). The resource 'properties' naturally separates it from the booking/room siblings, though no sibling is named explicitly.

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?

Usage is implied by the tool name/resource, and it notes 'Requires the properties scope' as a prerequisite. However, it gives no when-to-use vs alternative guidance and no exclusions, so an agent must infer context.

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