emergent_get_project

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

With no annotations, the description bears the burder of disclosing behavior; it does convey that this is a retrieval operation and names the returned content. It does not discuss staleness, authentication needs, or whether the call affects the project, but for a simple read-like GET this is an acceptable minimum.

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?

One efficient sentence front-loads the verb and resource ('Get full details'), listes the key output fields, and contains no filler. Every word contributes to the agent's understanding.

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 a single required parameter already documented by the schema and no output schema required, the description supplies enough context for an agent to call the tool appropriately. It could be slightly more complete by describing return shape or warning about prerequisites, but those are not essential for basic invocation.

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 only parameter, jobId, already has a schema description ('Job ID (UUID)'), so schema coverage is 100%. The tool description adds no additional semantic detail about the parameter beyond the implicit 'specific project' relationship, matching the baseline for full schema coverage.

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 says 'Get full details for a specific project' with a list of content fields (status, preview URL, credits used), so the action, resource, and scope are unambiguous. It does not explicitly differentiate from sibling tools such as emergent_get_preview, which also relate to preview URLs, but the singular 'specific project' makes it clearly distinct from list_projects.

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?

It implies this should be used when a single project's full details are needed, and the one required jobId reinforces that. However, it does not explicitly say when to prefer this over siblings like emergent_get_preview or emergent_get_creadits, nor does it provide exclusion criteria.

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