kitty.project.get

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Get a specific project' without disclosing whether the operation is read-only, what the response format looks like, or how errors are handled. This adds no information beyond the tool's name.

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 with clear structure. It is front-loaded with the action and resource, avoiding any unnecessary words.

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 the absence of an output schema and annotations, the description is too sparse to fully specify the tool's behavior. It does not mention what the returned project entity contains, any error conditions, or how to differentiate a successful retrieval from a missing project.

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 includes a single property 'projectSlug' with description 'Project slug', providing 100% parameter coverage. The tool description does not elaborate on this parameter or any parameter-specific behavior, so it adds no value beyond the schema, warranting the baseline score.

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 'Get a specific project' clearly identifies the action (get) and resource (project), and the qualifier 'specific' distinguishes it from the sibling tool kitty.projects.list which lists all projects. This makes the tool's purpose immediately clear.

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 provides no guidance on when to use this tool versus alternatives such as kitty.projects.list. There is no mention of the required projectSlug parameter or any prerequisites, leaving the agent to infer usage from the tool name and schema.

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