get_directory

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

No annotations are provided, so the description must cover behavioral traits. It states 'Returns JSON' implying a read operation, but does not explicitly confirm safety (no destructive side effects). For a simple read tool, this is adequate but not explicit.

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 front-loaded with the main purpose in the first sentence. It is concise with two paragraphs and an Args list. Minor redundancy (first sentence and second paragraph both mention return content), but overall efficient.

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 description explains the tool returns school details and staff records, and references get_staff_member for more detail. Given no output schema and one parameter, it provides sufficient context for a directory listing tool, though it could mention any limits or pagination.

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?

With 0% schema description coverage, the description must compensate. It lists 'school_id: School ID' in an Args section, providing minimal context beyond the schema. It does not give format or examples, but for a single integer parameter, the addition is functional.

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 lists school contact info and staff directory with names, roles, and phone numbers. It distinguishes from the sibling get_staff_member by noting that get_staff_member provides additional details like email and photo.

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 explicitly says when to use this tool ('List school contact info and staff directory') and when to use the alternative ('Use get_staff_member(school_id, user_id) for full staff details'). This provides clear guidance on tool selection.

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