get_projects

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

Discloses return format (numeric ID and display name), provides an example, and mentions using ID with submit_dsr(). With no annotations, this adequately describes behavior for a read-only listing tool.

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?

Concise four-sentence description with front-loaded purpose. Every sentence adds value: purpose, return format, example, usage hint.

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?

Fully covers purpose, usage, and return format. Output schema exists, so detailed return description isn't needed. Appropriate for a simple zero-parameter tool.

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?

No parameters, so schema coverage is 100%. Baseline 4 applies. Description adds value by explaining output format and usage beyond the empty schema.

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 states the tool lists projects for logging DSR hours, pulled from a specific dropdown. It distinguishes from siblings like get_my_projects by specifying the scope (all projects you can log DSR hours against).

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?

Explicitly says to call before submit_dsr() if you don't know the project_id. Provides clear context for when to use, though it doesn't mention when not to use or alternatives explicitly.

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