get_education

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

With no annotations, the description carries the full burden of behavioral disclosure. The verb 'Return' implies a read operation with no side effects, but it provides no additional behavioral context such as data source, permission requirements, or what exactly is included in 'education information'. The description stays at the surface level.

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, short sentence with no redundant words. It is appropriately sized for a parameterless read tool, though it lacks the richer detail that could still be conveyed compactly.

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 zero parameters and an output schema present, so the description need not explain return values. However, the description gives no context about when to use this tool relative to sibling profile getters, making the overall guidance feel incomplete for an agent that needs to disambiguate similar tools.

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 tool has zero parameters, so the description is not required to add parameter-level meaning. The schema already covers the empty parameter contract completely, and there is nothing further to explain.

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 states a clear verb ('Return') and resource ('education information'), making the tool's basic purpose unambiguous. However, it does not differentiate this from sibling getters like get_context or get_skills, which share a similar structure and could be confused when an agent is choosing among profile section retrievers.

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?

There is no guidance on when to use this tool versus its siblings. The description merely restates the function name without specifying contexts, exclusions, or alternatives, leaving the agent to infer usage solely from the tool name.

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