get_categories

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

The description adds hierarchy-structure behavior beyond the readOnlyHint annotation: it returns the full hierarchy and indicates the root level. This is useful context, though it could have been richer about ordering or response shape.

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?

Two sentences, front-loaded with the action and scope, followed by the intended use case. Every word earns its place with no repetition or filler.

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?

With no parameters and an output schema present, the description is complete for an agent to understand what the tool returns and when to call it. The hierarchy note and parentId hint cover the key conceptual context.

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?

Tool has 0 parameters, so the baseline is 4. The description adds helpful meaning about the parentId field and its role in the hierarchy, which helps an agent interpret the response even though there are no parameters.

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?

States a specific verb and resource: 'Get all categories and projects', and explicitly clarifies scope as 'the whole hierarchy' with parentId='root' as the top level. This distinguishes it clearly from siblings like get_children, which likely returns a narrower subset.

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?

Provides an explicit use case: 'Use to find the right parent_id when creating/moving.' This gives clear context for when the tool is valuable, though it does not mention explicit exclusions or alternative tools.

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