Api folders my assignments retrieve

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

The phrase "viewed or edited" asserts write capability while the annotations declare readOnlyHint=true and destructiveHint=false, an inconsistency that could lead an agent to treat this as a mutation endpoint. Beyond that conflict, the description discloses nothing about result scope (user's own assignments) or what data comes back.

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?

It is a single short sentence with no wasted clauses, so it is concise in form. However, the brevity comes from omission rather than efficiency: the one sentence says nothing specific about this endpoint's behavior.

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?

With zero parameters, annotations covering safety, and no output schema, the description was the only place to explain what "my assignments" returns and to whom. It omits that entirely, leaving the agent without the one piece of information this tool's name implies but does not confirm.

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 tool takes zero parameters, so the schema carries no semantics to document and the baseline for this dimension is 4. The description neither helps nor harms parameter understanding, since there is nothing to explain.

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 names only the generic resource ("folders") and says it can be "viewed or edited", which restates the boilerplate viewset title rather than the specific action. It never states the distinguishing fact implied by the tool name: that it returns folders assigned to the current user, so an agent cannot tell it apart from folders_list or folders_retrieve.

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?

There is no statement of when to use this endpoint, no mention of the personal/assignment scope, and no reference to alternatives such as ciso_assistant_api_folders_list or ciso_assistant_api_folders_object_retrieve. The agent is left to infer usage entirely from the tool name.

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