get-projects

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

No annotations exist, so the description carries the disclosure burden. It's a read-only retrieval described as 'Get' which implies safe read behavior, but it doesn't describe what the return format looks like, whether results are ordered, or how many projects are returned. Adequate but minimal for a no-annotation 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?

One clean, front-loaded sentence. Every word earns its place: the subject (Priya Gautam), the resource (projects), and the detail (with technologies). Zero waste.

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 read tool with no output schema, the description is appropriately complete. It names the resource and its key detail (technologies). Given the simplicity of the tool, little more is needed, though it could note the specific number/scope of projects returned.

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 zero parameters, so there's nothing for the description to add beyond the schema. The baseline for 0 params is 4, and the description correctly requires no inputs. No compensation needed.

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 verb (Get) and specific resource (Priya Gautam's major software projects and their technologies). It distinguishes from siblings like get-education and get-experience, and the proper noun clarifies whose projects are returned.

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 this is used when you need Priya Gautam's projects, but doesn't explicitly contrast with similar sibling tools like search-priya-profile or search-profile, which could also surface project info. No exclusions or alternative-recommendations provided.

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