list_projects

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

The description states the basic action but does not explain behavioral traits such as pagination, filtering, or sorting, despite these being available as parameters. Without annotations, the description should provide more context about how the tool behaves.

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, concise sentence that clearly states the tool's purpose. No unnecessary words, and it's well-structured for quick understanding.

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 is sufficient for basic understanding but lacks details about pagination, sorting, and the return structure. Given the number of parameters and the absence of an output schema, more context would be helpful.

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?

Since the input schema already provides full descriptions for all 6 parameters, the tool description does not add additional semantic meaning. The parameter descriptions are adequate, but the tool description does not compensate for any gaps.

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 clearly specifies the verb 'lists', the resource 'projects', and the scope 'within a specific Keyshade workspace'. This distinguishes it from sibling tools like list_workspaces and list_environments.

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 usage for listing projects in a workspace, but does not provide guidance on when to use this tool versus alternatives like global_search or other list tools. No exclusions or context for when not to use.

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