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

The description adds significant behavioral context beyond the standard read-only hint. By explicitly stating 'Metadata/approved fields only; no secrets, contacts or original files,' it manages expectations regarding data privacy and exposure, which is very valuable for an agent.

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 short and efficient. It places the primary behavioral constraint (data scope) at the end of the sentence, though a slightly better structure might have led with the core function.

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 that it takes 3 optional parameters (query, limit, offset), the description is missing context on how these parameters interact with the status data or what they filter/limit, relying heavily on the schema.

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 0%. Since the tool has 3 parameters (limit, query, offset), and the description adds no semantic meaning to these, it fails to compensate for the complete lack of schema-to-text alignment, resulting in a low score.

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 action ('Read' integration status) and the resource ('hotschedules integration status'). However, it is not specifically differentiated from the other numerous 'get_integration_status' sibling tools (e.g., get_7shifts_integration_status).

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 a read-only function, which matches the annotations. However, it does not provide explicit usage guidelines, such as when to use this tool over others or if there are specific conditions that necessitate this call.

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