upsert_profile

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

No annotations are provided, so the description must disclose behavioral traits. It reveals the upsert nature ('Create or update') and a parameter format (focus_areas comma-separated), but does not state whether existing data is overwritten, any auth requirements, or side effects. This is insufficient for a mutation 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?

The description is short and front-loaded with the core action. It wastes no words, though it is under-specified. As a concise statement, it is effective, but it sacrifices necessary detail.

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 mutation tool with no annotations and low schema coverage, the description is too sparse. It doesn't explain the relationship to matching/drafting workflows, or provide context on required fields or expected outcomes. An output schema exists, but the description still needs more context to be complete.

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?

Schema description coverage is 0%, so the description must add meaning for the 5 parameters. Only 'focus_areas' is explained (comma-separated). No guidance is given for profile_id, name, description, or github_url, leaving the agent to guess their roles.

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 states a clear action ('Create or update') on a specific resource ('project/researcher profile') and explains its purpose ('for matching and drafting'). This clearly distinguishes it from sibling tools that focus on grants and funding.

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 purpose implies when to use the tool (managing profiles), but there is no explicit guidance on when to use it instead of alternatives, nor any exclusions or prerequisites. The context 'for matching and drafting' gives some direction but is not explicit.

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