find_children

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

With no annotations, the description must carry the behavioral burden. 'Check before editing shared profiles' implies a read-only, non-destructive query, which is useful, but the description does not specify whether inheritance is direct or transitive, what the returned data looks like, or any additional behavior an agent should expect.

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 text is extremely short, with no filler, and the use-case directive follows the functional phrase immediately. The main structural weakness is the vague referent 'this one,' which adds ambiguity despite the concise format.

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 two unnamed parameters, no annotations, and no output schema, the description is too thin for an agent to call the tool confidently. It fails to explain how to populate name/type, what result to expect, and whether the child set is recursive, so the pre-edit check hint alone is incomplete.

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 exposes two required strings, 'name' and 'type', with zero descriptions, and the tool description never mentions either parameter. At 0% schema coverage, the description needed to compensate by explaining what values are valid, but it provides no parameter semantics at all.

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 identifies the resource as 'profiles inheriting from this one,' which tells the agent that the tool deals with descendant profiles, but it lacks an explicit verb such as 'find' or 'list' and reads as a sentence fragment. It does not distinguish this tool from sibling tools like list_profiles or get_chain, so the purpose is only inferable rather than precisely stated.

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?

'Check before editing shared profiles' gives a clear and actionable context: the tool should be invoked as a safety pre-check before modifications. It does not, however, name alternatives or state when this tool should not be used, so it stops short of full usage guidance.

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