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

Annotations are absent, so the description must disclose behavioral traits. It only mentions billing per call, but gives no information about side effects, authentication requirements, rate limits, or the nature of 'full' (e.g., whether it returns all education entries or just a subset). The read-only nature is implied by 'Get' but not explicitly stated.

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 remarkably concise, consisting of two short sentences. It front-loads the core purpose and includes essential billing information. However, the brevity leaves out critical details, and the billing note could be considered secondary but is still useful context.

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 the lack of annotations, output schema, and parameter documentation, the description is highly incomplete. It does not indicate what the response contains, whether further pagination is needed, or any error conditions. The phrase 'full education' is vague and could benefit from specifics like field names or coverage.

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%, and the description does not explain the 'urn' parameter at all. It only repeats the parameter name from the schema. The schema provides an example but no guidance on format or meaning. The description fails to compensate for the lack of parameter documentation.

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 'full education' data based on a URN. It specifies the resource (education) and the identifier (URN), making the core purpose unambiguous. However, it doesn't explicitly distinguish it from sibling tools like certifications or skills, though the name itself provides some differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that this should be used specifically for education history, nor does it mention any conditions or prerequisites (e.g., needing a valid URN). There is no comparison to similar profile endpoints.

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