get_projects

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Get' and 'current user' convey a read-only, user-scoped listing, but the description does not mention ordering, pagination, response shape, or whether any implicit filtering occurs. This is adequate for a simple list operation, but notable details remain implicit.

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 entire description is one short, front-loaded sentence with no filler words. Every word adds information about what the tool does and for whom.

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?

For a zero-parameter listing operation, the invocation is fully specified: call it with no arguments to retrieve the current user's projects. The lack of an output schema is a minor gap, but the expected type of result is reasonably self-evident from the tool's purpose.

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 tool has zero parameters, and the schema coverage is 100% by construction, so there are no parameter semantics for the description to clarify. This meets the baseline for a no-parameter tool, and the description does not need to add anything further.

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 ('Get'), resource ('projects'), and scope ('for the current user'), making the tool's purpose immediately clear. It is easily distinguished from siblings like create_project or get_project_summary, since it targets all projects for the current user rather than creating or summarizing 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 implies when to use the tool: whenever an agent needs all projects visible to the current user. However, it does not explicitly state when not to use it or mention alternatives such as get_project_summary, so the routing guidance is left largely to inference.

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