get_project_categories

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

The description is transparent about taking no arguments and describes the return format in detail (alphabetical order, message if none). However, it does not specify the scope of projects considered (e.g., all projects or only user's), which could be clarified. No annotations are provided, so the description carries the full burden.

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 concise (four sentences) and well-structured: purpose first, examples, use case, and return details. Every sentence adds value, and there is no redundancy.

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 description covers purpose, usage, and output format. It could be more explicit about whether categories span all projects or only active ones, but overall it is sufficient for a simple retrieval tool with no parameters.

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?

There are no parameters, and the input schema already indicates this. The description adds the statement 'Takes no arguments,' which confirms but does not add meaning beyond the schema. Baseline 3 is appropriate given 100% schema coverage.

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 explicitly states that the tool returns all distinct project categories currently in use, with examples ('Article', 'Grant', 'Teaching'). It clearly distinguishes from the sibling tool set_project_category by explaining the use case of offering an existing category before creating a new one.

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 directly tells when to use this tool: to list existing categories before using set_project_category, thereby preventing unnecessary creation of new ones. This provides clear guidance on selecting among siblings.

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