Get Facilities In Group

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

No annotations are provided, so the description carries full burden. It mentions limit/offset but does not disclose behavioral traits such as pagination behavior, sorting, error handling (e.g., if group not found), or rate limits. Minimal disclosure beyond schema.

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 sentence of 14 words, front-loading the purpose and including parameter hints. It is concise with no unnecessary verbiage.

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 a tool with 3 parameters (1 required), schema coverage 100%, and an output schema, the description adequately states core functionality. It does not explain return values, but that is covered by the output schema. Could add a note about behavior when facilityGroupId is invalid.

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 100% with each parameter having a description. The description adds 'optional limit and offset parameters' but this is already evident from the schema. No additional semantic meaning is provided beyond what the input schema already conveys.

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 tool retrieves facilities belonging to a specific facility group, using the verb 'get' and resource 'facilities in group'. It distinguishes from sibling tools like garoon-get-facilities (all facilities) and garoon-get-facility-groups (list groups).

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 when you want facilities within a specific group (by providing facilityGroupId), but it does not explicitly state when to use this over alternatives like garoon-get-facilities. No when-not or alternative tool names are mentioned.

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