Edit your Snapp ride profile (name, gender, address, birthdate) using a dry-run preview. Confirm explicitly to apply changes.
Edit profile (dry-run)
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| token | No | ||
| gender | No | ||
| address | No | ||
| confirm | No | ||
| birthdate | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. "Edit profile (dry-run)" is contradictory: 'edit' implies mutation while 'dry-run' implies no persistence, and the tool offers no clarification of which is true, what auth is required, or what the confirm parameter does.
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?
Very short, but not in an earned way — three words plus a parenthetical that actively misleads. Under-specification is not conciseness.
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 6-parameter profile-mutation tool with zero annotations, zero schema docs, and no output schema, three words plus an ambiguous '(dry-run)' is grossly inadequate. No confirmation flow, no auth requirements, no dry-run vs real-run semantics.
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% across 6 parameters, and the description mentions none of them. Nothing explains what 'token', 'confirm', or the PII-shaped fields (address, birthdate, gender) mean or how 'confirm' interacts with the claimed dry-run behavior.
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?
"Edit profile" states a verb and resource, but the parenthetical "(dry-run)" is ambiguous and the name 'ride_profile_set' versus sibling 'ride_profile_show' isn't clearly distinguished. An agent cannot confidently tell whether this persists changes or only previews them.
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?
No when-to-use guidance at all. It doesn't distinguish itself from ride_profile, ride_profile_show, or any of the 45+ siblings. The contradictory '(dry-run)' hint offers no routing information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.