kreta_guardian_profile

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the account-level scoping ('bejelentkezett fiók') but does not explain how the optional 'child' parameter changes behavior, authentication needs, or any other operational traits.

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 Hungarian sentence with no filler. It states the operation and scope directly and earns every word, though it sacrifices explanatory richness for brevity.

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 that all parameters are optional and an output schema exists, the description is minimally sufficient for a no-argument call. However, it is incomplete for correct advanced invocation because the 'child' parameter is unexplained, and there is no guidance on when to pick this tool over the sibling student-profile tool.

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 schema has one parameter, 'child', with 0% description coverage, and the tool description does not mention it at all. The description therefore adds no meaning beyond the raw schema, leaving an agent unable to tell what 'child' is for or how it affects the retrieved profile.

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 names a specific operation ('lekérése' = retrieval) and a specific resource ('gondviselői adatlap' = guardian profile) scoped to the logged-in account. It clearly distinguishes this tool from the sibling 'kreta_student_profile' by specifying the guardian-facing profile rather than the student profile.

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 implies the tool should be used when the guardian profile of the logged-in account is needed, but it does not explicitly state when to use it versus alternatives, nor does it give any exclusions. Sibling tools like 'kreta_student_profile' exist, but no routing guidance is provided.

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