Listar Projetos do Ekyte

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

Annotations indicate readOnly, destructive false, idempotent, openWorld. Description adds useful behavioral details like filtering with is_planning and endpoint override, without contradicting annotations. No extra info on auth or rate limits 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?

Two sentences, front-loaded with main purpose, zero fluff. Every sentence adds value.

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?

Adequately covers the main functionality and key parameters. No output schema, but description hints at return format via response_format param. Lacks default ordering or pagination details, but schema covers page param.

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 coverage is 100%, but description adds value beyond schema for key parameters: explains is_planning purpose and endpoint_override use case. Other params are well-described in schema.

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 it lists projects from the company in Ekyte, with specific guidance on using is_planning and endpoint override. It distinguishes from sibling tools like ekyte_create_project by being a read operation.

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?

Provides clear context for using is_planning=1 to find projects with planned but inactive tasks, and mentions endpoint override. However, it does not explicitly compare with sibling list tools (e.g., ekyte_list_tasks) to guide when to use this vs others.

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