get_resource_assignments

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

Describes filtering behavior (partial vs exact match) and enrichment, but omits other behavioral traits like required file_path, default limit, or output format. With no annotations, more disclosure needed.

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?

Concise with bullet points for parameters; no redundant information. Could be slightly more compact but overall well-structured.

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?

Covers essential filtering but lacks details on output, pagination, and error handling. With sibling tools providing alternative data, more context on when to use this specific tool would improve completeness.

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?

Explains two parameters (rsrc_name, task_code) with matching details, compensating for 0% schema coverage. However, file_path and limit remain unexplained, leaving gaps.

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 tool retrieves resource-activity assignments with enriched names. It distinguishes from siblings like get_resources and get_project_activities by focusing on assignments.

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 on when to use this tool versus alternatives such as get_relationships or analyze_resource_utilization. Lacks context for selection.

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