Get Project Custom Field Values

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

With no annotations, description discloses the paginated return format and chunking behavior, but could mention read-only nature or permissions.

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?

Two focused sentences: first states purpose, second explains return structure and rationale for model. No extraneous content.

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?

Adequate for a simple get with pagination; covers return format and pagination. Lacks error conditions or limit details but sufficient given schema coverage.

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 covers all 4 parameters (100% coverage), baseline 3. Description adds value by linking page/size to pagination in return format, slightly exceeding baseline.

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?

Description clearly states the tool gets available values for a custom field with pagination, distinct from sibling 'project_get_custom_fields' which lists custom fields themselves.

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?

Description implies paginated use but does not explicitly specify when to use this tool versus alternatives like project_get_custom_fields or how to handle pagination.

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