openpanel_get_project

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

No annotations provided, so description carries full burden. While 'Get' implies read-only operation, no details provided about return format, pagination, caching behavior, or what 'settings and statistics' specifically encompasses. No mention of auth requirements or rate limits.

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?

Extremely brief single sentence (excluding [UNIFIED] tag). Front-loaded with action verb. While concise, the '[UNIFIED]' prefix appears to be metadata noise that doesn't earn its place in the description text.

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?

Given 0% schema coverage, missing output schema, no annotations, and a complex sibling tool ecosystem with overlapping concerns (get_project_settings, get_project_stats), the description is incomplete. It should clarify the relationship to specific-setting tools and document the parameters it requires.

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 description coverage is 0% (neither 'site' nor 'project_id' documented in schema), and description completely fails to compensate. No explanation of what 'site' refers to (domain? site ID? URL?) or expected format of 'project_id'. Agent has no semantic guidance for parameter values.

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?

Clear verb 'Get' with resource 'project' and scope 'details including settings and statistics'. However, it doesn't clarify how this differs from sibling tools like 'openpanel_get_project_settings' or 'openpanel_get_project_stats', creating potential ambiguity about whether this is a composite view or alternative to specific getters.

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 provided on when to use this versus 'openpanel_list_projects' (single vs. bulk retrieval) or the specific settings/stats tools. No prerequisites or conditions mentioned despite the specific parameter requirements.

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