evolution_profile_fetch_privacy

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

The description only states the action and resource, without disclosing behavioral traits like idempotency, permission requirements, or error handling. With no annotations provided, the agent lacks insight into side effects or constraints.

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 a single, front-loaded sentence with no unnecessary words. It efficiently conveys the core purpose.

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 simple fetch tool with one optional parameter and no output schema, the description is adequate but could improve by hinting at the output format (e.g., JSON object with privacy settings).

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 schema already describes the only parameter 'instance' with 100% coverage, including its optionality. The tool description adds no further semantic value beyond that.

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 uses a specific verb 'Fetch' and clearly identifies the resource as 'the instance's privacy settings', distinguishing it from sibling tools like evolution_profile_fetch (general profile) and evolution_profile_update_privacy (update).

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 guidance is provided on when to use this tool versus alternatives, such as evolution_profile_fetch for broader profile data or evolution_profile_update_privacy for modifications. There is no mention of prerequisites or context.

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