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. It does not state whether the tool is read-only, whether it requires specific permissions, or what happens on invocation. The phrase 'Owner or office' hints at access restriction but is not developed enough to cover the missing 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 compact sentence with no wasted words. However, it front-loads the resource rather than an explicit action verb, and 'Owner or office' is somewhat cryptic.

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 is simple with one parameter and has an output schema, so return values need not be explained. Still, with no annotations and a minimal description, key context is missing: whether it is read-only, how it relates to phone_setEmergency, and what the single shop_id parameter expects.

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?

There is one required parameter, shop_id, but the schema description coverage is 0% and the description does not mention it at all. Even though shop_id is a common identifier, the description adds no meaning beyond the bare schema name.

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 identifies the resource as the shop's emergency call handling configuration and mentions suggested trigger words, but it lacks an explicit verb such as 'get' or 'retrieve'. It does not explicitly distinguish itself from the sibling phone_setEmergency, though the name and content imply a read operation.

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 only usage context is 'Owner or office', which appears to be a permission or audience note rather than guidance on when to use this tool versus alternatives. There is no explicit when-to-use, when-not-to-use, or mention of phone_setEmergency or phone_voiceAi as alternatives.

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