getCredentialStatus

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

Discloses read-only nature, that secrets are never exposed, account-scoping requiring linked Extentos account, and permission gating (Credentials access grant). Details error responses (401, 403) for authentication and authorization failures. No contradictions with annotations (none provided).

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?

Description is front-loaded with core functionality and return shape, then adds important caveats and usage guidance. While slightly verbose, every sentence provides value. Could be marginally tighter but still 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?

For a tool with no output schema, the description covers return shape, error conditions, authentication requirements, permission model, and usage context. It is fully self-contained and provides all necessary information for an agent to use it correctly.

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 already describes the single required parameter 'appPackage' as 'The app\'s package / bundle id (project_install_id).' The description does not add additional parameter-level information beyond what the schema provides, but schema coverage is 100% so baseline 3 is appropriate.

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?

Clearly states the tool reads whether a project's Meta DAT build identity is set, plus a masked hint and update time. Specifies the return structure. Distinguishes from siblings by explicitly stating not to use for reading secret values and directs to setCredential for adding.

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?

Explicitly says when to use (check before recommending setup, confirm after setCredential) and when not to use (never to read a secret value). Provides alternative tool (setCredential) for adding credentials.

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