get_orgs_by_career_level

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

No annotations are provided, so the description must convey behavioral traits beyond the basic function. It only states what the tool does (find orgs by career level) and does not disclose side effects, authentication needs, rate limits, pagination, or output format. This is insufficient for a tool with no 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 sentence with no unnecessary words. It is front-loaded and efficient. However, it could benefit from slight expansion to improve completeness without losing conciseness.

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?

With no output schema, the description should explain what the tool returns (e.g., list of organization names/IDs). It does not. The tool is simple but the missing information could lead to incorrect expectations. The sibling context suggests it returns student organizations, but this is not explicit.

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?

The input schema has 100% coverage with a description and enum for the single parameter. The description adds no further meaning; it only repeats the enum values in parentheses. Thus, it provides no additional value beyond the schema, earning a baseline 3.

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 'Find organizations for specific career levels' with a verb and resource, and lists the possible levels. This distinguishes it from sibling tools like 'get_student_organizations' (likely listing all orgs) and 'get_orgs_by_type' (filtering by type). However, it does not explicitly say what is returned (e.g., names, IDs), so it is not maximally specific.

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 provides no guidance on when to use this tool versus alternatives like 'search_student_orgs' or 'get_orgs_by_type'. There is no mention of when not to use it or what prerequisites exist, which limits effective tool selection.

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