get_concept

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

No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation, and the mention of 'current mastery' discloses a key output detail. However, the description does not explicitly state the absence of side effects, authentication requirements, or error behavior, which is a moderate gap for a tool without annotation support.

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, front-loaded sentence that directly states the tool's purpose and key output. There is no superfluous information, making it highly concise and well-structured.

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 two required parameters and no output schema, so the description is mostly adequate for invocation. However, it does not clarify the exact return format or other details beyond 'current mastery', and it lacks usage context relative to sibling tools. This leaves some gaps but remains usable.

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 fully describes both parameters (studentId and conceptId) with clear descriptions, achieving 100% schema coverage. The description adds no extra meaning beyond what the schema already provides, so the baseline of 3 applies.

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 uses the clear verb 'Get' and identifies the resource as 'details about a specific concept' with the added scope 'for a student' and 'including current mastery'. It is specific enough to differentiate from siblings like explain_concept and get_mastery_heatmap, though 'details' is somewhat vague about what other information is returned.

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 explicit guidance on when to use this tool versus alternatives such as get_mastery_heatmap or explain_concept. The phrase 'a specific concept' implies single-concept use, but no exclusions or alternative tools are mentioned, leaving the agent without sufficient context for selection.

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